Uploaded image for project: 'Maistra'
  1. Maistra
  2. MAISTRA-446

Operator deploys next component even if previous component not ready

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • maistra-rc1
    • None
    • operator
    • None
    • RC1

      During the process of deploying a control plane, the operator deploys a component and then waits for its deployment(s) to be ready before deploying the next component (implemented in waitForDeployment()). If the deployment doesn't become ready in about a minute, the function logs "deployment failed to become ready in a timely manner" and returns an error, but the error isn't handled and the operator then deploys the next component.

      It seems like it shouldn't continue. Otherwise, why would we include the wait if the system tolerates deploying subsequent components even when previous ones aren't ready?

      One thing to note is that if the operator didn't continue, the deployment process would be stuck due to the citadel/prometheus ordering bug described in MAISTRA-445.

              rcernich1 Rob Cernich
              mluksa@redhat.com Marko Luksa (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: