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

Update Operator Metadata for ClusterResourceOverride Operator in Preparation for 4.18 Release

XMLWordPrintable

    • Important
    • None
    • 3
    • PODAUTO - Sprint 262
    • 1
    • Proposed
    • False
    • Hide

      None

      Show
      None

      The build job for the clusterresourceoverride-admission-operator is failing due to ineffective metadata updates in the preparation for the 4.18 release. The following errors have been logged:

      2024-10-10 00:42:08,478 artcommonlib ERROR [containers/clusterresourceoverride-operator] Search `clusterresourceoverride-operator.v4.18.0` and replace was ineffective for clusterresourceoverride-operator
      2024-10-10 00:42:08,529 artcommonlib ERROR [containers/clusterresourceoverride-operator] Search `version: 4.18.0` and replace was ineffective for clusterresourceoverride-operator
      2024-10-10 00:42:08,584 artcommonlib ERROR [containers/clusterresourceoverride-operator] Search `olm.skipRange: ">=4.3.0 <4.18.0"` and replace was ineffective for clusterresourceoverride-operator
      

      Proposed Solution:

      Refer to the implementation in another project, specifically the PTP Operator, for a similar issue resolution. It is essential to carefully evaluate the differences between the projects before applying any changes to ensure compatibility and correctness.

      Action Items:

      • Review the error logs and identify the specific areas where the metadata update is failing.
      • Compare the implementation in the PTP Operator to determine the necessary changes.
      • Apply the relevant changes to the clusterresourceoverride-operator metadata.
      • Test the build job post-implementation to ensure it passes successfully.

              joelsmith.redhat Joel Smith
              lgarciaac Luis GarcĂ­a Acosta
              Sunil Choudhary Sunil Choudhary
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: