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
      Previously, when mirroring operator catalogs, `oc-mirror` would rebuild the catalogs and regenerate their internal cache based on `imagesetconfig` catalog filtering specifications. This process required the `opm` binary from within the catalogs. Starting with version 4.15, operator catalogs include the `opm` {op-system-base} 9 binary, which caused the mirroring process to fail when executed on {op-system-base} 8 systems. With this update, `oc-mirror` no longer rebuilds catalogs by default; instead, it simply mirrors them to their destination registries.
      To retain the catalog rebuilding functionality, use `--rebuild-catalog`. However, note that no changes were made to the current implementation, so using this flag may result in the cache not being generated or the catalog not being deployed to the cluster. Also, if you use this command, you can export `OPM_BINARY` to specify a custom `opm` binary that corresponds to the catalog versions and platform found in {product-title}.
      With this update, mirroring of catalog images is done without signature verification. Use `--enable-operator-secure-policy` to enable signature verification during mirroring.
      (link:https://issues.redhat.com/browse/OCPBUGS-31536[*OCPBUGS-31536*])
      Show
      Previously, when mirroring operator catalogs, `oc-mirror` would rebuild the catalogs and regenerate their internal cache based on `imagesetconfig` catalog filtering specifications. This process required the `opm` binary from within the catalogs. Starting with version 4.15, operator catalogs include the `opm` {op-system-base} 9 binary, which caused the mirroring process to fail when executed on {op-system-base} 8 systems. With this update, `oc-mirror` no longer rebuilds catalogs by default; instead, it simply mirrors them to their destination registries. To retain the catalog rebuilding functionality, use `--rebuild-catalog`. However, note that no changes were made to the current implementation, so using this flag may result in the cache not being generated or the catalog not being deployed to the cluster. Also, if you use this command, you can export `OPM_BINARY` to specify a custom `opm` binary that corresponds to the catalog versions and platform found in {product-title}. With this update, mirroring of catalog images is done without signature verification. Use `--enable-operator-secure-policy` to enable signature verification during mirroring. (link: https://issues.redhat.com/browse/OCPBUGS-31536 [* OCPBUGS-31536 *])
    • Bug Fix
    • Done
    • Customer Escalated

      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
              Subhashini T K Subhashini T K
              Votes:
              9 Vote for this issue
              Watchers:
              34 Start watching this issue

                Created:
                Updated:
                Resolved: