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

Operator doesn't check for deployment failures

    XMLWordPrintable

Details

    • 0

    Description

      Background: In a scenario where a malformed custom Quay Config Bundle was attached to the QuayRegistry object, the Quay pods kept crash looping because they weren't able to find specific settings. In this situation the Operator remains in "MigrationsInProcess" state which will never finish.

      Expected results: The Operator recognizes if deployments are failing and report that in the status block. This is probably covered by: PROJQUAY-1609

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. PROJQUAY-1812 Quay config app changes are not rolled out if QuayRegistry status in MigrationInprogress

          • 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

          Activity

            People

              rmarasch@redhat.com Ricardo Maraschini (Inactive)
              DanielMesser Daniel Messer
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: