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

`oc mirror --config` command failed with exit status 1

XMLWordPrintable

    • No
    • CLID Sprint 252, CLID Sprint 253
    • 2
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      When mirroring operator catalogs, `oc-mirror` rebuilds the catalogs and regenerates their internal cache according to `imagesetconfig` catalog filtering specifications. This operation requires the use of the `opm` binary found within the catalogs. In 4.15, operator catalogs include the `opm` RHEL 9 binary, causing the mirroring process to fail when running on RHEL 8 systems.
      With this fix, by default, `oc-mirror` no longer rebuilds catalogs. It simply mirrors them to the destination registry.
      For users who would like to keep the functionality of catalog rebuilding, please use the --rebuild-catalogs flag. Please be aware though that no change to the current implementation was done. Therefore, using this flag might lead to oc-mirror failing to generate the cache, or the catalog failing to deploy to the cluster (original bug).
      Furthermore, users enforcing --rebuild-catalog might want to force oc-mirror to use a custom opm binary (the one corresponding to the catalog versions being mirrored as well as their OS and platform) by exporting the environment variable OPM_BINARY. The opm binary can be found in https://mirror.openshift.com/pub/openshift-v4/clients/ocp/.
      Show
      When mirroring operator catalogs, `oc-mirror` rebuilds the catalogs and regenerates their internal cache according to `imagesetconfig` catalog filtering specifications. This operation requires the use of the `opm` binary found within the catalogs. In 4.15, operator catalogs include the `opm` RHEL 9 binary, causing the mirroring process to fail when running on RHEL 8 systems. With this fix, by default, `oc-mirror` no longer rebuilds catalogs. It simply mirrors them to the destination registry. For users who would like to keep the functionality of catalog rebuilding, please use the --rebuild-catalogs flag. Please be aware though that no change to the current implementation was done. Therefore, using this flag might lead to oc-mirror failing to generate the cache, or the catalog failing to deploy to the cluster (original bug). Furthermore, users enforcing --rebuild-catalog might want to force oc-mirror to use a custom opm binary (the one corresponding to the catalog versions being mirrored as well as their OS and platform) by exporting the environment variable OPM_BINARY. The opm binary can be found in https://mirror.openshift.com/pub/openshift-v4/clients/ocp/ .
    • Bug Fix
    • In Progress

      Description of problem:

          While mirroring with the following command[1], it is observed that the command fails with error[2] as shown below:
~~~
[1] oc mirror --config=imageSet-config.yaml docker://<registry_url>:<Port>/<repository>
~~~

~~~
[2] error: error rebuilding catalog images from file-based catalogs: error regenerating the cache for <registry_url>:<Port>/<repository>/community-operator-index:v4.15: exit status 1
~~~

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

      How reproducible:

          100%

      Steps to Reproduce:

          1. Download `oc mirror` v:4.15.0 binary
    2. Create ImageSet-config.yaml
    3. Use the following command:
~~~
oc mirror --config=imageSet-config.yaml docker://<registry_url>:<Port>/<repository>
~~~
    4. Observe the mentioned error

      Actual results:

          Command failed to complete with the mentioned error.

      Expected results:

         ICSP and mapping.txt file should be created.

      Additional info:

            skhoury@redhat.com Sherine Khoury
            rhn-support-harspati Harshada Patil
            Rama Kasturi Narra Rama Kasturi Narra
            Votes:
            5 Vote for this issue
            Watchers:
            20 Start watching this issue

              Created:
              Updated: