-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrading Cassandra Version 3 to 4 not possible #1110
Comments
On an additional note: after Alexander told me that the creation of the configuration has been changed with Cassandra 4.1+, I tried upgrading my cluster to 4.0.10 (cass-management-api not available for 4.0.11) before upgrading to 4.1.2. The upgrade to 4.0.10 worked, but when trying to upgrade to 4.1.2 the same error as mentioned above occurs. |
It relates to k8ssandra/k8ssandra-client#17 |
This is fixed in k8ssandra-operator v1.10.3 which was released a few minutes ago. |
What happened?
When trying to upgrade the Cassandra version from 3.11.16 to 4.1.2 the upgrade fails, because of a cluster name mismatch.
Did you expect to see something different?
The cluster name should not change, and the upgrade should work flawless.
How to reproduce it (as minimally and precisely as possible):
Environment
K8ssandra Operator version:
1.10.1
Kubernetes version information:
Server Version: v1.24.17
Kubernetes cluster kind:
Rancher
Manifests:
Anything else we need to know?:
A downgrade to 3.11.16 after manually modifying the stateful set is also not possible. No logs printed.
The text was updated successfully, but these errors were encountered: