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

CannotRetrieveUpdates should provide command-line next-step advice

XMLWordPrintable

    • Low
    • No
    • False
    • Hide

      None

      Show
      None
    • N/A
    • Release Note Not Required

       Description of problem:

      The CannotRetrieveUpdates alert currently provides a link to the web-console so the responding admin can find the RetrievedUpdates=False message. But some admins lack convenient console access (e.g. they're SSHing in to a restricted network or the cluster does not have the Console capability enabled. Those admins would benefit from oc ... command-line advice.

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

      The alert is new in 4.6:

      $ for Y in $(seq 5 12); do git --no-pager grep CannotRetrieveUpdates "origin/release-4.${Y}"; done | head -n1
origin/release-4.6:docs/user/status.md:When CVO is unable to retrieve recommended updates the CannotRetrieveUpdates alert will fire containing the reason. This alert will not fire when the reason updates cannot be retrieved is NoChannel.

      and has never provided command-line advice.

      How reproducible:

      Consistently.

      Steps to Reproduce:

      1. Install a cluster.
      2. Set an impossible channel, such as oc adm upgrade channel testing.
      3. Wait an hour.
      4. Check firing alerts in /monitoring/alerts.
      5. Click through to CannotRetrieveUpdates.

      Actual results:

      Failure to retrieve updates means that cluster administrators...

      description does not provide oc ... advice.

      Expected results:

      Failure to retrieve updates means that cluster administrators...

      description does provide oc ... advice.

            [OCPBUGS-23290] CannotRetrieveUpdates should provide command-line next-step advice

            Errata Tool added a comment -

            Since the problem described in this issue should be resolved in a recent advisory, it has been closed.

            For information on the advisory (Critical: OpenShift Container Platform 4.15.0 bug fix and security update), and where to find the updated files, follow the link below.

            If the solution does not work for you, open a new bug report.
            https://access.redhat.com/errata/RHSA-2023:7198

            Errata Tool added a comment - Since the problem described in this issue should be resolved in a recent advisory, it has been closed. For information on the advisory (Critical: OpenShift Container Platform 4.15.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2023:7198

            W. Trevor King added a comment -

            I set No Doc Update, because it's not worth release notes for this minor tweak.

            W. Trevor King added a comment - I set No Doc Update , because it's not worth release notes for this minor tweak.

            OpenShift Jira Bot added a comment -

            Hi lmohanty@redhat.com,

            Bugs should not be moved to Verified without first providing a Release Note Type("Bug Fix" or "No Doc Update") and for type "Bug Fix" the Release Note Text must also be provided. Please populate the necessary fields before moving the Bug to Verified.

            OpenShift Jira Bot added a comment - Hi lmohanty@redhat.com , Bugs should not be moved to Verified without first providing a Release Note Type("Bug Fix" or "No Doc Update") and for type "Bug Fix" the Release Note Text must also be provided. Please populate the necessary fields before moving the Bug to Verified.

              lmohanty@redhat.com Lalatendu Mohanty
              trking W. Trevor King
              Yang Yang Yang Yang
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: