This repository has been archived by the owner on Jan 29, 2024. It is now read-only.
Failure in HA upgrading from 15.1.1 to 16.0.1 #377
Labels
Comments
|
I did such upgrade without any problems but to version 16.1.1 instead of 16.0.1. I had the same config you mentioned above regarding clustering. So maybe it is better to skip version 16.0.1. |
|
I got the same error upgrading from 15.1.1 to 16.1.1 |
|
What I understand from this issue is that Infinispan nodes from Keycloak 15 cannot coexist with the ones from Keycloak 16. |
|
Does anyone know any way to update the KeyCloak cluster without losing all the sessions from 15.1.1 to a higher KeyCloak version? Have you figured it out? |
Not me. I just down scaled my cluster, upgrade and restart all nodes. (it was acceptable for my use cases..) |
|
Got the same kind of error upgrading from 17.0.1 to 18.0.2. Workaround in kubernetes is to set replicas to 0 then set to previous scale again. Log on a preexisting cluster member (17.0.1): Log on the new (18.0.2) cluster member: |
|
With Keycloak 20 the WildFly based distribution is no longer supported. For the newer Quarkus distribution of Keycloak, check out the new documentation, or the updated container sources. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
When upgrading from 15.1.1 to 16.0.1 the new container hungs during infinispan sincronization with following error:
Update: similar problem going from 17.0.1 to 18.0.2 (see #377 (comment))
Version
16.1.1
Expected behavior
Expected behavior is a clean upgrade.
Actual behavior
No response
How to Reproduce?
Keycloak on Kubernetes clustered with:
Anything else?
Upgrade from 15.1.1 directly to 16.1.1 suffers from the same.
The full log:
The text was updated successfully, but these errors were encountered: