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

4.16.z released after the maintenance phase ends should default to the eus-4.16 update channel

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Moderate
    • No
    • None
    • None
    • In Progress
    • Bug Fix
    • Hide
      Previously, {product-title} release 4.16.55 and earlier releases remained on the stable-4.16 channel instead of switching to the eus-4.16 channel. This could cause 'VersionNotFound' errors when attempting to retrieve update information and since the version is not found in the stable-4.16 channel, the recommended updates are not available. With this release, the installer directs 4.16.56 and later releases to the Extended Update Support (EUS) channel ensuring the releases receive recommended update notices and the `VersonNotFound` error no longer displays. (link:https://issues.redhat.com/browse/OCPBUGS-73879[OCPBUGS-73879])
      Show
      Previously, {product-title} release 4.16.55 and earlier releases remained on the stable-4.16 channel instead of switching to the eus-4.16 channel. This could cause 'VersionNotFound' errors when attempting to retrieve update information and since the version is not found in the stable-4.16 channel, the recommended updates are not available. With this release, the installer directs 4.16.56 and later releases to the Extended Update Support (EUS) channel ensuring the releases receive recommended update notices and the `VersonNotFound` error no longer displays. (link: https://issues.redhat.com/browse/OCPBUGS-73879 [ OCPBUGS-73879 ])
    • None
    • None
    • None
    • None

      Description of problem

      4.16 left the maintenance phase and entered the EUS phase on 2025-12-27. We want 4.16.z that enter fast-4.16 up through that time to keep being added to stable-4.16, but 4.16.z that enter fast-4.16 after that date to only be added to eus-4.16 (and no longer get added to stable-4.16), to help folks who don't meet the EUS qualifications stay on releases that they have support for. I'm a bit late this time around, but catching up now, only a bit past that EUS transition. This change would give users in the default channel access to patch updates they qualify for, assuming only folks with EUS qualifications are installing 4.16.z releases during the EUS lifecycle phase.

      Version-Release number of selected component

      Only the 4.16 installer needs updating, to reflect this 4.16-lifecycle-phase transition.

      How reproducible

      Every time.

      Steps to Reproduce

      1. Install a 4.16.z cluster.
      2. Check its current channel, e.g. with oc adm upgrade | grep Channel.

      Actual results

      Channel: stable-4.16 (...)

      Expected results

      stable-4.16 for 4.16.younger, but starting with EUS-era 4.16.larger, eus-4.16.

              trking W. Trevor King
              trking W. Trevor King
              None
              None
              Gaoyun Pei Gaoyun Pei
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: