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

Backport vendor runtime-utils to support both ICSP and IDMS objects

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • 4.13.z
    • 4.13.z
    • Node / Kubelet
    • No
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      Cause: previously we disallow the coexistence of ICSP with IDMS/ITMS
      Consequence: to use the newer IDMS or ITMS objects, you needed to delete any ICSP objects
      Fix: allow ICSP, IDMS, ITMS objects existing on the same cluster. The spec of source, mirror mappings will be merged to the /etc/containers/registries.cof.
      Result: you can use any or all of the three types of objects to configure repository mirroring after the cluster is installed.
      Show
      Cause: previously we disallow the coexistence of ICSP with IDMS/ITMS Consequence: to use the newer IDMS or ITMS objects, you needed to delete any ICSP objects Fix: allow ICSP, IDMS, ITMS objects existing on the same cluster. The spec of source, mirror mappings will be merged to the /etc/containers/registries.cof. Result: you can use any or all of the three types of objects to configure repository mirroring after the cluster is installed.
    • Bug Fix
    • In Progress

      Description of problem:

      This Bug is for OCPNODE-1799  backport to 4.13.z

      backport https://github.com/openshift/machine-config-operator/pull/3898

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

       

      How reproducible:

       

      Steps to Reproduce:

      1.
2.
3.

      Actual results:

       

      Expected results:

       

      Additional info:

       

            [OCPBUGS-23468] Backport vendor runtime-utils to support both ICSP and IDMS objects

            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 (Important: OpenShift Container Platform 4.13.z 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:7827

            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 (Important: OpenShift Container Platform 4.13.z 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:7827

            Min Li added a comment - - edited

            verified!

            % oc get clusterversion 
            NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
            version   4.13.0-0.nightly-2023-12-11-165920   True        False         158m    Cluster version is 4.13.0-0.nightly-2023-12-11-165920

            Both ICSP and IDMS/ITMS objects wrote to registries.conf well.

            Min Li added a comment - - edited verified! % oc get clusterversion  NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS version   4.13.0-0.nightly-2023-12-11-165920   True        False         158m    Cluster version is 4.13.0-0.nightly-2023-12-11-165920 Both ICSP and IDMS/ITMS objects wrote to registries.conf well.

            Qi Wang added a comment -

            Moved to POST status although MCP PR got merged. This can not be verified without https://github.com/openshift/kubernetes/pull/1798.

            Qi Wang added a comment - Moved to POST status although MCP PR got merged. This can not be verified without https://github.com/openshift/kubernetes/pull/1798 .

            OpenShift Jira Bot added a comment -

            Hi qiwan233,

            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 qiwan233 , 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.

              qiwan233 Qi Wang
              qiwan233 Qi Wang
              Min Li Min Li
              Qi Wang
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: