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

Quay config app changes are not rolled out if QuayRegistry status in MigrationInprogress

    XMLWordPrintable

Details

    • 0

    Description

      Quay/Quay -operator 3.4.3

      Scenario:

      Install Quay/Quay-operator provide storage details in the config bundle secret , This storage uses a self signed certificate, so Quay-app upgrade will fail to start.

      Now launch Quay config editor try adding the CA certs and click validate, after successful validation click "reconfigure quay". 

       

      The reconfiguration never happens, although there is a new secret created , Quay config app upgrade will continue to fail, Also deleting quay-app-upgrade, quay-operator pods doesnt help either, the new operator doesnt reconcile since the migration is in progress. Only option would be to delete the quayregistry CR and update the config bundle with the certs and recreate quayregistry.

       

       

       

      Attachments

        Issue Links

          account is impacted by

          Task - Represents a small unit of work that is not end-user facing. PROJQUAY-3028 Release v3.6.3

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          causes

          Bug - A problem that impairs or prevents the functions of the product. PROJQUAY-2060 Quay operator project remains in Terminating

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is duplicated by

          Bug - A problem that impairs or prevents the functions of the product. PROJQUAY-2174 Quay operator has difficulties rescaling the upgrade deployment

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. PROJQUAY-2046 Operator continuously reconciles QuayRegistry

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. PROJQUAY-2068 Operator doesn't check for deployment failures

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          links to

          GitHub quay/quay-operator#591: refactor: nuke goroutine polling migrations

          GitHub quay/quay-operator#613: controller: update condition reason when upgrade job crashes

          Activity

            People

              fmissi Flavian Missi
              rhn-support-dgangaia Dixit Gangaiah (Inactive)
              luffy zhang luffy zhang
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: