Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-59801

CI job for OIDC on AKS fails to parse latest Auth configuration

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Normal Normal
    • None
    • 4.19.z, 4.20.0
    • HyperShift
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Important
    • None
    • None
    • None
    • Proposed
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:
      The job for testing OIDC fails to deploy hosted cluster due to invalid OIDC configuration. The configuration is applied in this step.
      The Console cluster operator fails to start with this error:

      - lastTransitionTime: "2025-07-18T04:12:09Z"
          message: |-
            AuthStatusHandlerDegraded: error converting obj to typed: .spec.oidcProviders[name="microsoft-entra-id"].claimMappings.extra: field not declared in schema
            CLIAuthStatusHandlerDegraded: error converting obj to typed: .spec.oidcProviders[name="microsoft-entra-id"].claimMappings.extra: field not declared in schema
          reason: AuthStatusHandler_FailedApply::CLIAuthStatusHandler_FailedApply
      

      The console-operator fails at authentication.go#L57.
      The schema for TokenClaimMappings is hardcoded in internal.go which is a vendored "client-go" dependency at version github.com/openshift/client-go v0.0.0-20250402181141-b3bad3b645f2 (from April 2)
      However, the "extra" and "uid" config elements were merged in client-go later on April 25 as part of this PR.
      The console operator needs another bump of client-go library so as to be able to consume the new elements in configuration.
      The current version of client-go used by console operator doesn't included the required changes on all recent branches (main, release-4.20, release-4.19)

      Version-Release number of selected component (if applicable):

      4.19, 4.20

      How reproducible:

      Always

      Steps to Reproduce:

          1. Run the job for 4.20: https://qe-private-deck-ci.apps.ci.l2s4.p1.openshiftapps.com/job-history/gs/qe-private-deck/logs/periodic-ci-openshift-openshift-tests-private-release-4.20-amd64-nightly-azure-aks-hypershift-ext-oidc-tp-guest-f14
          2. Or, run the job for 4.19: https://qe-private-deck-ci.apps.ci.l2s4.p1.openshiftapps.com/job-history/gs/qe-private-deck/logs/periodic-ci-openshift-openshift-tests-private-release-4.19-amd64-nightly-azure-aks-hypershift-ext-oidc-tp-guest-f14
          

      Actual results:

      The hosted cluster doesn't properly start due to Console cluster operator failing.
          

      Expected results:

      The hosted cluster starts successfully.
          

      Additional info:

      
          

              mgencur@redhat.com Martin Gencur
              mgencur@redhat.com Martin Gencur
              None
              None
              Martin Gencur Martin Gencur
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: