Uploaded image for project: 'Project Quay'
  1. Project Quay
  2. PROJQUAY-6054

Using Red Hat Config tool to make config changes in Quay Instance not working

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Normal
    • None
    • None
    • config-tool
    • False
    • None
    • False
    • Moderate
    • 0

    Description

      Description of problem:

      We have the Red Hat Quay Operator installed on a OCP 4.11.40 Cluster.  We deployed and configured a Quay Registry instance, with all the pre-req components running and ready.  The Quay Registry instance is operating as expected, and we can logon to the registry endpoint using a user that we created.  We can successfully create and access the repositories.
      
      We then use the Red Had Quay Config Tool to change the default internal authentication from `Local Database` to `LDAP`.  We successfully run the Validate Configuration Changes and push the updates to the Red Hat Quay Operator.  We observe the registry instance pods restart to pickup the changes to the configuration.  The exact pods that restart have the names *quay-config-editor* and *quay-mirror*. 
      
      We then reload the Red Hat Quay logon page from the browser to verify if the authentication has changed to LDAP.  It has not changed and is still using the local database for its authentication.  It is not until we manually delete the pods with the name *quay-app* when the new configuration changes take hold. It would seem that the changes that are pushed out from the config tool do not automatically restart the app pods and user must manually delete.

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

      4.11.40

      How reproducible:

      Consistently

      Steps to Reproduce:

      1. Logon to Quay Config Tool
      2. Make a configuration change under Internal Authentication from Local Database to LDAP
      3. Provide the necessary LDAP information to your private ldap server.
      4. Select "Validate Configuration Changes" to validate with ldap server. Successfully shows "Configuration Validated"
      5. Select "Reconfigure Quay" to push the updates to the operator.  Successfully shows "Config Sent to Operator"
      6. Observe Red Hat Quay instnace pods restart
      7. Verify from Red Hat Quay logon endpoint is now using LDAP.  Fails since it is still using the default 'local database' for authentication.

      Actual results:

      Changes made to the internal authentication through Config Tool does not work.

      Expected results:

      Changes made to the internal authentication through Config Tool should be pushed to Operator.

      Additional info:

      Only when manually deleting the quay-app pods do the new changes take effect.

      Attachments

        Activity

          People

            Unassigned Unassigned
            phchan@redhat.com Phil Chan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: