OpenTelemetry Logs and Keycloak build steps cycle

[Malandril]

Describe the bug

When activating open telemetry logs and oidc with keycloak devservice in one project the build fails with cyclic dependencies.

aused by: io.quarkus.builder.ChainBuildException: Cycle detected:
                   io.quarkus.oidc.deployment.devservices.keycloak.KeycloakDevUIProcessor#produceProviderComponent produced class io.quarkus.arc.deployment.SyntheticBeanBuildItem
                to io.quarkus.arc.deployment.SyntheticBeansProcessor#initRuntime produced class io.quarkus.arc.deployment.BeanRegistrationPhaseBuildItem$BeanConfiguratorBuildItem
                to io.quarkus.arc.deployment.ArcProcessor#registerSyntheticObservers produced class io.quarkus.arc.deployment.ObserverRegistrationPhaseBuildItem
                to io.quarkus.arc.deployment.ArcProcessor#validate produced class io.quarkus.arc.deployment.ValidationPhaseBuildItem
                to io.quarkus.arc.deployment.ArcProcessor#validateAsyncObserverExceptionHandlers produced class io.quarkus.arc.deployment.ValidationPhaseBuildItem$ValidationErrorBuildItem
                to io.quarkus.arc.deployment.ArcProcessor#generateResources produced class io.quarkus.arc.deployment.ResourcesGeneratedPhaseBuildItem
                to io.quarkus.arc.deployment.ArcProcessor#initializeContainer produced class io.quarkus.arc.deployment.ArcContainerBuildItem
                to io.quarkus.arc.deployment.ArcProcessor#notifyBeanContainerListeners produced class io.quarkus.arc.deployment.PreBeanContainerBuildItem
                to io.quarkus.arc.deployment.ArcProcessor#signalBeanContainerReady produced class io.quarkus.arc.deployment.BeanContainerBuildItem
                to io.quarkus.opentelemetry.deployment.logging.LogHandlerProcessor#build produced class io.quarkus.deployment.builditem.LogHandlerBuildItem
                to io.quarkus.deployment.logging.LoggingResourceProcessor#setupLoggingRuntimeInit produced class io.quarkus.deployment.logging.LoggingSetupBuildItem
                to io.quarkus.devservices.keycloak.KeycloakDevServicesProcessor#startKeycloakContainer produced class io.quarkus.devservices.keycloak.KeycloakDevServicesConfigBuildItem
                to io.quarkus.oidc.deployment.devservices.keycloak.KeycloakDevUIProcessor#produceProviderComponent
        at io.quarkus.builder.BuildChainBuilder.detectCycles(BuildChainBuilder.java:327)

Expected behavior

No response

Actual behavior

No response

How to Reproduce?

Create a project with both dependencis
quarkus create app quarkus-oidc-otel --gradle-kotlin-dsl --extension='rest-jackson,opentelemetry,oidc' -P 'io.quarkus.platform:quarkus-bom:3.17.5'

Add otel logs

echo 'quarkus.otel.exporter.otlp.enabled=true' >> quarkus-oidc-otel/src/main/resources/application.properties
echo 'quarkus.otel.logs.enabled=true' >> quarkus-oidc-otel/src/main/resources/application.properties

Then run quarkus dev

Output of uname -a or ver

linux

Output of java -version

21

Quarkus version or git rev

3.17.5

Build tool (ie. output of mvnw --version or gradlew --version)

8.12

Additional information

Should not be a duplicate of #45130 as the fix should be already included in quarkus 3.17.5

[quarkus-bot]

/cc @brunobat (opentelemetry), @geoand (kotlin), @pedroigor (keycloak), @radcortez (opentelemetry), @sberyozkin (keycloak)

[geoand]

This is similar to #45130, but it's likely harder to address

[michalvavrik]

I'll have a look.

[michalvavrik]

It can only be reproduced with 3.17.5, but not with the 999-SNAPSHOT. I suspect we just need to backport #44590.

[brunobat]

It makes sense #44590 will fix the issue because it's not using a synthetic bean anymore.

[javanegmond]

It can only be reproduced with 3.17.5, but not with the 999-SNAPSHOT. I suspect we just need to backport #44590.

FWIW, this also happens on 3.17.3.

Also FWIW: disabling keycloak devservices (quarkus.keycloak.devservices.enabled=false [1]) does not alleviate the issue.

[1] https://quarkus.io/guides/security-openid-connect-dev-services#disable-dev-services-for-keycloak

[michalvavrik]

thanks for info @javanegmond , all of that is aligned with our conclusion. I don't think you can work around that, but it's a DEV mode issue, so it has zero impact on production and tests.

[geoand]

Closing this as the problem does not exist in main