Ensure gRPC server starts after Otel is configured (if applicable)

[geoand]

• Fixes: Constructor injection of io.opentelemetry.api.metrics.Meter in a @GrpcService-annotated class makes tests fail #47062

[brunobat]

I can add an IT test to the PR... We don't have a specific test just with gRPC, without Quarkus Rest.

[geoand]

I updated the PR to add Opentelemetry to one of the existing ones

[brunobat]

Double checked and the test does not reproduce the condition on my machine.
Will add a new, simpler IT test, if you don't mind.

[geoand]

Of course, go right ahead

[brunobat]

The fix sounds good @geoand.
I was thinking on an IT test like this for a while... I even have one in a draft somewhere, for other reasons.

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 9fec960.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

[alesj]

What about if we're more specific / exact, to "wait" for OTel, not an entire ArC?
e.g. to add some new build item, if needed ...

[geoand]

I tried one of the BuildItem classes we already have in OTel and unfortunately it didn't work because although gRPC server started after OTel, the OTel bean is lazy and still caused the same problem

[brunobat]

The issue still happens from time to time. From the CI:
https://ge.quarkus.io/s/ycjt4yea2ryuu/tests/goal/io.quarkus:quarkus-integration-test-opentelemetry-grpc-only:surefire:test@default-test/details/io.quarkus.it.opentelemetry.grpc.HelloGrpcClientTest/testHello?expanded-stacktrace=WyIwIiwiMC0xMSJd&top-execution=2

[geoand]

Nice 🙂