Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-33657

Ingress Operator always remains in the progressing state

XMLWordPrintable

    • +
    • Important
    • Yes
    • 12
    • Sprint 254, NE Sprint 255, NE Sprint 256
    • 3
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      *Cause*: The ingress operator goes to Progressing state when the number of "available replicas" is less than the number of "updated replicas". This can happen when the deployment information is being updated more often than it really is, such as updates without actual changes (spurious updates).

       *Consequence*: The cluster ingress operator is seen to be in status Progressing=true for prolonged periods, more so when there are a larger number of replicas. A message like this one shows up in the log:

      ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 16 of 18 updated replica(s) are available...)

      *Fix*: Several bugs addressing spurious updates were backported all the way to to release 4.12

      *Result*: Fewer spurious updates are made and the number of updated replicas should be closer to the number of available replicas during an upgrade.
      Show
      *Cause*: The ingress operator goes to Progressing state when the number of "available replicas" is less than the number of "updated replicas". This can happen when the deployment information is being updated more often than it really is, such as updates without actual changes (spurious updates).  *Consequence*: The cluster ingress operator is seen to be in status Progressing=true for prolonged periods, more so when there are a larger number of replicas. A message like this one shows up in the log: ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 16 of 18 updated replica(s) are available...) *Fix*: Several bugs addressing spurious updates were backported all the way to to release 4.12 *Result*: Fewer spurious updates are made and the number of updated replicas should be closer to the number of available replicas during an upgrade.
    • Bug Fix
    • In Progress
    • Customer Escalated

      Description of problem:

          Ingress Operator always remain in the progressing state

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

          4.12.40

      How reproducible:

          Always in customer enviornment

      Summary:

      The cluster operator ingress always remains in the progressing state with the message that current replicas doesn't match to the desired replicas. However, the when checking number of pods in openshift-ingress it matches the number of replicas defined in ingresscontroller. 

      Adding more details in the comment section.

       

              cholman@redhat.com Candace Holman
              rhn-support-hchaturv Himank Chaturvedi
              Shudi Li Shudi Li
              Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated:

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 week, 3 days
                  1w 3d