Uploaded image for project: 'OpenShift Builds'
  1. OpenShift Builds
  2. BUILD-779

Shipwright Operator reports "Ready" too early

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • OpenShift-Builds-1.0
    • shipwright
    • 5
    • False
    • None
    • False
    • 5
    • Pipeline Integrations #2260, Builds Sprint #5
    • Low

      Description of problem:

      The Shipwright operator reports the "Ready" condition on the ShipwrightBuild object before any of its operands are actually ready. At best this is misleading - at worse it might miss the fact that an operand (ex build controller) is no longer stable.

      Workaround

      None

      Prerequisites (if any, like setup, operators/versions):

      • Shipwright Operator v0.12.0 or equivalent deployed on cluster (builds for OpenShift v1.0)

      Steps to Reproduce

      1. Deploy Shipwright Operator
      2. Create a ShipwrightBuild object (target namespace openshift-builds)
      3. Watch the "Ready" condition of the object while watching the pods in the target namespace (openshift-builds)

      Actual results:

      ShipwrightBuild marks itself "Ready" before the build controller and conversion webhook pods are ready

      Expected results:

      ShipwrightBuild does not mark itself "Ready" until all of its operands are "Ready"

      Reproducibility (Always/Intermittent/Only Once):

      Always

      Acceptance criteria: 

      Definition of Done:

      Build Details:

      Additional info (Such as Logs, Screenshots, etc):

       

       *

            rh-ee-asatyam Ayush Satyam
            adkaplan@redhat.com Adam Kaplan
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: