Hide Forgot
Description of the problem: e2e-operator pre-submit e2e jobs are failing on all releases (down to at least 4.8) due to a failure of the test `TestKeycloakAsOIDCPasswordGrantCheckAndGroupSync` (called `TestKeycloakAsOIDCPasswordGrantCheck` 4.9 and older releases). * Debug PR triggering tests against master yields: https://prow.ci.openshift.org/pr-history/?org=openshift&repo=cluster-authentication-operator&pr=549 * Debug PR triggering tests against release-4.9 yields: https://prow.ci.openshift.org/pr-history/?org=openshift&repo=cluster-authentication-operator&pr=547 * Debug PR triggering tests against release-4.8 yields: https://prow.ci.openshift.org/pr-history/?org=openshift&repo=cluster-authentication-operator&pr=550
It was raised in keycloak/keycloak-quickstarts#300 but no update yet, FYI.
> It was raised in keycloak/keycloak-quickstarts#300 but no update yet, FYI. After a conversation with Alex Szczuczko and Dominik Guhr from the RH SSO (Keycloak) team, I suspect that the mismatch between API and docs will be solved by fixing the docs. The patch that I propose (attached to this BZ) entails pinning our code to the "legacy" variant of Keycloak's 17.0.0 image, which exhibits the old behaviour. This patch is designed to be backported down to at least 4.8 to unblock the corresponding presubmit tests in the cluster-authentication-operator repository. I believe that a valid follow-up will be to change the code to use the non-legacy variant: that is, issuing a "start" or "start-dev" command in the container startup.
The action plan: 1. Fix 4.11 by adapting the test logic to Keycloak v17 (see https://github.com/openshift/cluster-authentication-operator/pull/554) 2. Fix previous cluster-authentication-operator releases by pinning Keycloak to the "legacy" (WildFly) variant of v17
closing CURRENTRELEASE as the tests are now successful, and there is no need for this test-only change to hit the release notes.