Describe the bug
When cassandra is deployed in isolation, it gets stuck in Waiting for Database until some other event wakes it up (e.g. juju relate or update-status).
To Reproducejuju deploy --edge cassandra-k8s
This also happens with the latest version from main.
Expected behavior
When deployed in isolation, the charm should end up in Active, or in Blocked, prompting the user to form a relation, without relying on update-status.
Describe the bug When cassandra is deployed in isolation, it gets stuck in
Waiting for Database
until some other event wakes it up (e.g. juju relate or update-status).To Reproduce
juju deploy --edge cassandra-k8s
This also happens with the latest version from main.
Expected behavior When deployed in isolation, the charm should end up in
Active
, or inBlocked
, prompting the user to form a relation, without relying on update-status.Environment