closes: #45576

Failing just as quarkus-next is - it appears that the java operator sdk may not be appropriately updated yet.

@metacosm is the operator sdk ready for quarkus 3.31.0?

Yes but we don't have a release for it yet. I can do it now, if needed, though.

Yes but we don't have a release for it yet. I can do it now, if needed, though.

@metacosm yes please. There seems to be an incompatiblity currently:

Error:  Failed to execute goal io.quarkus:quarkus-maven-plugin:3.31.0.CR1:build (default) on project keycloak-operator: Failed to build quarkus application: io.quarkus.builder.BuildException: Build failure: Build failed due to errors
Error: [ERROR] 	[error]: Build step io.quarkiverse.operatorsdk.deployment.AddNamespaceEnvVarBuildStep#addNamespaceEnvVar threw an exception: java.lang.NoSuchMethodError: 'io.quarkus.kubernetes.spi.KubernetesEnvBuildItem io.quarkus.kubernetes.spi.KubernetesEnvBuildItem.createSimpleVar(java.lang.String, java.lang.String, java.lang.String, boolean[])'
Error:  	at io.quarkiverse.operatorsdk.deployment.AddNamespaceEnvVarBuildStep.lambda$addNamespaceEnvVar$0(AddNamespaceEnvVarBuildStep.java:15)
Error:  	at java.base/java.util.HashMap$Values.forEach(HashMap.java:1073)
Error:  	at io.quarkiverse.operatorsdk.deployment.AddNamespaceEnvVarBuildStep.addNamespaceEnvVar(AddNamespaceEnvVarBuildStep.java:12)
Error:  	at java.base/java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:733)
Error:  	at io.quarkus.deployment.ExtensionLoader$3.execute(ExtensionLoader.java:898)
Error:  	at io.quarkus.builder.BuildContext.run(BuildContext.java:255)

Yes but we don't have a release for it yet. I can do it now, if needed, though.

@metacosm yes please. There seems to be an incompatiblity currently:

Error:  Failed to execute goal io.quarkus:quarkus-maven-plugin:3.31.0.CR1:build (default) on project keycloak-operator: Failed to build quarkus application: io.quarkus.builder.BuildException: Build failure: Build failed due to errors
Error: [ERROR] 	[error]: Build step io.quarkiverse.operatorsdk.deployment.AddNamespaceEnvVarBuildStep#addNamespaceEnvVar threw an exception: java.lang.NoSuchMethodError: 'io.quarkus.kubernetes.spi.KubernetesEnvBuildItem io.quarkus.kubernetes.spi.KubernetesEnvBuildItem.createSimpleVar(java.lang.String, java.lang.String, java.lang.String, boolean[])'
Error:  	at io.quarkiverse.operatorsdk.deployment.AddNamespaceEnvVarBuildStep.lambda$addNamespaceEnvVar$0(AddNamespaceEnvVarBuildStep.java:15)
Error:  	at java.base/java.util.HashMap$Values.forEach(HashMap.java:1073)
Error:  	at io.quarkiverse.operatorsdk.deployment.AddNamespaceEnvVarBuildStep.addNamespaceEnvVar(AddNamespaceEnvVarBuildStep.java:12)
Error:  	at java.base/java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:733)
Error:  	at io.quarkus.deployment.ExtensionLoader$3.execute(ExtensionLoader.java:898)
Error:  	at io.quarkus.builder.BuildContext.run(BuildContext.java:255)

Interesting, I haven't seen that error when upgrading to 3.31.0.CR1. I'm not even sure why it's reporting an error there because we're not calling a createSimpleVar(String, String, String, boolean[]) method at all. We're calling KubernetesEnvBuildItem.createSimpleVar(String, String, String) at that spot…

We've release 7.5.0.CR1 targeting Quarkus 3.31.0.CR1.

We've release 7.5.0.CR1 targeting Quarkus 3.31.0.CR1.

Thank you @metacosm !

Hopefully the JOSDK update will address the operator failures.

The logging failure in the IT tests has been addressed - also #45642 was captured.

This still leaves 3 other failures.

cc @keycloak/cloud-native

@mabartos added another commit to address the trace logging - there's been some kind of change where we now have quarkus-bootstrap-runner as a transitive dependency in keycloak services and that cause the log initializer to default to showing trace enabled. Added an exclusion, but a quarkus fix may be applicable too.

cc @keycloak/cloud-native

Looks like #45679 addresses the issue with QOSDK.

Looks like #45679 addresses the issue with QOSDK.

Thank you @metacosm. Do you know what the timeline should look like for this to be included? Or should we just go ahead and move forward with temporary version override for now?

Looks like #45679 addresses the issue with QOSDK.

Thank you @metacosm. Do you know what the timeline should look like for this to be included? Or should we just go ahead and move forward with temporary version override for now?

The goal is to get the final version in the 3.31 platform by next week. Since it seems that the issue is addressed with CR1, we will go ahead with the final release so that we can get included in the 3.31 platform. /cc @xstefank

@keycloak/cloud-native moved to 3.31.1, but not quite there yet. There's a javascript test failure and the storage tests are failing due to a low-level issue:

2026-01-28T20:54:45.6689676Z Caused by: java.lang.NullPointerException: Cannot invoke "java.util.List.forEach(java.util.function.Consumer)" because the return value of "org.hibernate.sql.exec.spi.LoadedValuesCollector.getCollectedCollections()" is null
2026-01-28T20:54:45.6690234Z 	at org.hibernate.sql.exec.internal.lock.LockingHelper.logLoadedValues(LockingHelper.java:478)
2026-01-28T20:54:45.6690943Z 	at org.hibernate.sql.exec.internal.lock.FollowOnLockingAction.performPostAction(FollowOnLockingAction.java:102)
2026-01-28T20:54:45.6691748Z 	at org.hibernate.sql.exec.internal.JdbcSelectWithActions.performPostAction(JdbcSelectWithActions.java:122)
2026-01-28T20:54:45.6701603Z 	at org.hibernate.sql.exec.internal.JdbcSelectExecutorStandardImpl.doExecuteQuery(JdbcSelectExecutorStandardImpl.java:220)
2026-01-28T20:54:45.6702438Z 	at org.hibernate.sql.exec.internal.JdbcSelectExecutorStandardImpl.executeQuery(JdbcSelectExecutorStandardImpl.java:100)
2026-01-28T20:54:45.6702986Z 	at org.hibernate.sql.exec.spi.JdbcSelectExecutor.executeQuery(JdbcSelectExecutor.java:63)
2026-01-28T20:54:45.6703447Z 	at org.hibernate.sql.exec.spi.JdbcSelectExecutor.list(JdbcSelectExecutor.java:137)

I'll look into that more tomorrow.