"Failed to validate database" issue when initializing keycloak #29032
Replies: 1 comment
-
Note At the time of writing, I'm not affiliated, associated, authorized, endorsed by, or in any way officially connected with Red Hat. Since you seem to be using the Red Hat build of open-source projects, I assume you're a paying customer, in which case you're probably elegible for Red Hat support. From what I understand, RHSSO 7.4 was released on April 8, 2020 and it's technology preview, therefore it's unsupported and should not be used in production. rhsso-7.6 was released on June 30, 2022 and its upstream project was archived on Nov 16, 2022. The first commercial version of Keycloak is based on Keycloak 22, and its corresponding operator is called rhbk-operator.
|
Beta Was this translation helpful? Give feedback.
-
Hello all,
I have an rhsso-operator managed operator inside OpenShift which spawns all the required keycloak resources and spins up a keycloak pod connected to an external postgres database.
When the pod starts up, I'm seeing the following:
Looking at the postgres logs I have confirmed that the pod has connectivity to the database, it even attempts to create a new table whenever it is spun up for the first time:
At first I thought the error could be that this specific table already existed (as pointed in the postgres logs), so I backed it up with a different name and spun up the pod again - it created the table on startup, but then crashed with that same error.
I've looked at the method that throws the error but wasn't able to extracted much information from it other than it seeming to be some sort of post-startup database validation.
Does anyone have any idea what this could be related with? I've checked every single operator-managed configuration and everything seems to be correct, even in comparing to similar environments.
This may be helpful:
Thank you.
Beta Was this translation helpful? Give feedback.
All reactions