Uploaded image for project: 'Managed Service - API'
  1. Managed Service - API
  2. MGDAPI-5788

Addon installation stuck due to user existing in SSO

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • None
    • None
    • None
    • RHOAM Sprint 43, RHOAM Sprint 44, RHOAM Sprint 45

      WHY
      Time to time SREs will get alerted about clusters with Install of RHOAM addon has exceeded timeout. When investigating, SREs have noticed that the installation is failing due to duplicate users in SSO instance.
      SREs used to have access to user-sso edge route, which was removed sometime back.
      We have created a JIRA to add that back in MGDAPI-5785
      Note that above route is not going to help when it is a private cluster.

      WHAT
      Requesting a SOP that guides SREs on how to remove an offending user entry by removing the entry in the user-sso DB.

      HOW
      If the KeycloakUser CR has a 409 conflict error we can delete the user from Keycloak to allow the CR to reconcile.

      We may need to implement this for cluster SSO and user SSO

      TESTS
      <List of related tests>

      DONE
      <bullet point items for what should be completed>

              mstoklus_rhmi Michal Stokluska
              cabeywar-cssre Chamal Abeywardhana
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: