Václav Muzikář
Václav Muzikář
So it is a regression in 26.
Not a release blocker as it affects only a preview feature (OTEL Tracing).
@shawkins Thank you for creating the follow-up for the Operator. While I'd love to take this aggressive approach and just remove the no-longer-needed fields (as it's the last opportunity to...
> They can't upgrade until all Keycloaks no longer use the deprecated field. This is the main issue I see. The typical scenario (for RHBK but upstream possibly as well)...
@shawkins I'd like to resurrect the discussion here. If we remove the fields, users can't install KC 24/25 alongside 26 in the same cluster, correct? If that's the case, I'm...
> @vmuzikar jfyi - I'm a little bit worried about the 409 Conflict flakiness. Could you please check them as well once you finish the work on this? This turned...
I was not able to track down the flakiness of HostnameV2Test yet. It's not really specific to that test, running it separately doesn't reproduce it, only as part of the...
@mabartos I'm not sure if we should create more issues as they are not really relevant without the Quarkus upgrade. I tried to provide most details in the PR description....
Spent some more time debugging the flaky hostname test and turned out to be much deeper issue: https://github.com/keycloak/keycloak/issues/32785. Nevertheless, since it affects just H2, I'd like to still proceed with...
Given the nature of the changes, adding more reviewers.