Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-8171

Provide transparency around newer to older release "updates"

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • updates
    • None
    • Product / Portfolio Work
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      1. Proposed title of this feature request
      Provide transparency around newer to older release "updates"

      2. What is the nature and description of the request?
      Creating this RFE to support the Epic https://issues.redhat.com/browse/OTA-1352

      3. Why does the customer need this? (List the business requirements here)
      In order to match cluster versions across a fleet, customer had a need to update to an older version of the next y-stream release. While updating through four y-streams, the upgrade path that had previously existed according to our graph tool disappeared, so the cluster arrived at a dead end.

      4. List any affected packages or components.
      Cincinnati and the OpenShift Update Service (OSUS)

              rh-ee-smodeel Subin M
              rhn-support-cshepher Christine Shepherd
              None
              Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                None
                None