Open gberche-orange opened 6 years ago
This error means the password for the cassandra
admin user is not the default cassandra
and not the one that the deployment specifies.
This typically happens when you try to set a new value to the cassandra_password
property. In v6, you can never change the value of this property.
You must upgrade to v8 in order to benefit from the password update feature (#48) for the cassandra
admin user.
Plus, there is now a dedicated cassandra-deployment
Git repo for the v8, which eases things a lot when it comes to writing a COA deployment. Everything is easier with v8. You should not use v6 anymore.
If you don't mind, we'll close this issue.
We observe randomly the following symptom with v0.6 release. We're not yet sure whether the root cause comes from the environment (bosh director or infrastructure) or from the cassandra 0.6 release.
However, after a few minutes the deployment status displays the nodes as running
Looking at
/var/vcap/sys/log/cassandra/post-start.stderr.log
on cassandra-seeds/41da6c3c-0d85-4049-b5b6-7ee8b34f6cfa we repeatedly seefollowing is the associated bosh deployment manifest
additional release
/CC @JCL38-ORANGE @poblin-orange