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

DNS operator reports degraded when simply progressing during a 4.14 upgrade

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • 4.14.0
    • Networking / DNS
    • Moderate
    • No
    • Sprint 239, Sprint 240, Sprint 241, Sprint 242, Sprint 243, Sprint 244, Sprint 245, Sprint 246, Sprint 247, Sprint 248, Sprint 249, Sprint 250, Sprint 251, Sprint 252, Sprint 253, Sprint 254, NE Sprint 255, NE Sprint 256, NE Sprint 257, NE Sprint 258, NE Sprint 259, NE Sprint 260, NE Sprint 261, NE Sprint 262, NE Sprint 263, NE Sprint 264
    • 26
    • Rejected
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      During the upgrade of build02 cluster, we observed DNS operator reporting Degraded condition while workers were being upgraded, without any apparent degradation and while DNS operator was simultaneously reporting Progressing=True condition.

      Based on OpenShift guidelines the operators should not report Degraded=True and Progressing=True at the same time and during an upgrade.

      Additionally, the Degraded=True condition's reason field was simply saying Reason: DNSDegraded which is not helpful (this string is surfaced to users in the UIs).

      Degraded operators during an upgrade cause the UIs to report the upgrade process is problematic, so this creates unwanted noise.

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

      During upgrade from 4.14.0-ec.0 to 4.14.0-ec.1

      How reproducible:

      Unsure

              cholman@redhat.com Candace Holman
              afri@afri.cz Petr Muller
              Melvin Joseph Melvin Joseph
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated: