Downgrading from 26.7.0 to 26.0 fails with liquibase ValidationFailedException on a changeset checksum, which is stricter than an unknown migration: the old version knows the changeset but its definition differs. The pod goes CrashLoopBackOff and never starts. The StatefulSet stopped the rollout at the first pod, so the other kept serving and the front door stayed at 200, which replica 1 would not have done. The failed start never touched the schema, so restoring the image was enough; had the migration already applied, the D-1 database restore would have been the only way back. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
21 lines
1.0 KiB
Plaintext
21 lines
1.0 KiB
Plaintext
=== 서비스는 살아 있는가 (StatefulSet 롤링이 막아줬다) ===
|
|
https://auth.hyeonworks.com/realms/master HTTP 200
|
|
Warning: v1 Endpoints is deprecated in v1.33+; use discovery.k8s.io/v1 EndpointSlice
|
|
ready 주소: [10.42.1.140]sed: -e expression #1, char 27: unknown option to 's'
|
|
|
|
=== Liquibase 오류 상세 ===
|
|
2026-09-04 06:03:25,877 ERROR [org.keycloak.quarkus.runtime.cli.ExecutionExceptionHandler] (main) ERROR: liquibase.exception.ValidationFailedException: Validation Failed:
|
|
1 changesets check sum
|
|
2026-09-04 06:03:25,877 ERROR [org.keycloak.quarkus.runtime.cli.ExecutionExceptionHandler] (main) ERROR: Validation Failed:
|
|
1 changesets check sum
|
|
|
|
=== ★ 앞으로 되돌린다 (26.7.0) ===
|
|
statefulset.apps/keycloak image updated
|
|
partitioned roll out complete: 2 new pods have been updated...
|
|
keycloak-0 1/1 Running 0 10m
|
|
keycloak-1 1/1 Running 0 28s
|
|
|
|
=== 데이터는 무사한가 ===
|
|
realms|clients|migrations|sessions = 2|15|210|4
|
|
외부 진입점 HTTP 200
|