|
| 1 | +// Module included in the following assemblies: |
| 2 | +// |
| 3 | +// * installing/disconnected_install/installing-mirroring-disconnected-v2.adoc |
| 4 | + |
| 5 | +:_mod-docs-content-type: PROCEDURE |
| 6 | +[id="oc-mirror-troubleshooting-v2_{context}"] |
| 7 | +== Troubleshooting oc-mirror plugin v2 errors |
| 8 | + |
| 9 | +oc-mirror plugin v2 now logs all image mirroring errors in a separate file, making it easier to track and diagnose failures. |
| 10 | + |
| 11 | +[IMPORTANT] |
| 12 | +==== |
| 13 | +When errors occur while mirroring release or release component images, they are critical. This stops the mirroring process immediately. |
| 14 | +
|
| 15 | +Errors with mirroring Operators, Operator-related images, or additional images do not stop the mirroring process. Mirroring continues, and oc-mirror plugin v2 logs updates every 8 images. |
| 16 | +==== |
| 17 | + |
| 18 | +When an image fails to mirror, and that image is mirrored as part of one or more Operator bundles, oc-mirror plugin v2 notifies the user which Operators are incomplete, providing clarity on the Operator bundles affected by the error. |
| 19 | + |
| 20 | +.Procedure |
| 21 | + |
| 22 | +. Check for server-related issues: |
| 23 | ++ |
| 24 | +.Example error |
| 25 | +[source,terminal] |
| 26 | +---- |
| 27 | +[ERROR] : [Worker] error mirroring image localhost:55000/openshift/graph-image:latest error: copying image 1/4 from manifest list: trying to reuse blob sha256:edab65b863aead24e3ed77cea194b6562143049a9307cd48f86b542db9eecb6e at destination: pinging container registry localhost:5000: Get "https://localhost:5000/v2/": http: server gave HTTP response to HTTPS client |
| 28 | +---- |
| 29 | + |
| 30 | +.. Open the `mirroring_error_date_time.log` file in the `working-dir/logs` folder located in the oc-mirror plugin v2 output directory. |
| 31 | +.. Look for error messages that typically indicate server-side issues, such as `HTTP 500` errors, expired tokens, or timeouts. |
| 32 | +.. Retry the mirroring process or contact support if the issue persists. |
| 33 | + |
| 34 | +. Check for incomplete mirroring of Operators: |
| 35 | ++ |
| 36 | +.Example error |
| 37 | +[source,terminal] |
| 38 | +---- |
| 39 | +error mirroring image docker://registry.redhat.io/3scale-amp2/zync-rhel9@sha256:8bb6b31e108d67476cc62622f20ff8db34efae5d58014de9502336fcc479d86d (Operator bundles: [3scale-operator.v0.11.12] - Operators: [3scale-operator]) error: initializing source docker://localhost:55000/3scale-amp2/zync-rhel9:8bb6b31e108d67476cc62622f20ff8db34efae5d58014de9502336fcc479d86d: reading manifest 8bb6b31e108d67476cc62622f20ff8db34efae5d58014de9502336fcc479d86d in localhost:55000/3scale-amp2/zync-rhel9: manifest unknown |
| 40 | +error mirroring image docker://registry.redhat.io/3scale-amp2/3scale-rhel7-operator-metadata@sha256:de0a70d1263a6a596d28bf376158056631afd0b6159865008a7263a8e9bf0c7d error: skipping operator bundle docker://registry.redhat.io/3scale-amp2/3scale-rhel7-operator-metadata@sha256:de0a70d1263a6a596d28bf376158056631afd0b6159865008a7263a8e9bf0c7d because one of its related images failed to mirror |
| 41 | +error mirroring image docker://registry.redhat.io/3scale-amp2/system-rhel7@sha256:fe77272021867cc6b6d5d0c9bd06c99d4024ad53f1ab94ec0ab69d0fda74588e (Operator bundles: [3scale-operator.v0.11.12] - Operators: [3scale-operator]) error: initializing source docker://localhost:55000/3scale-amp2/system-rhel7:fe77272021867cc6b6d5d0c9bd06c99d4024ad53f1ab94ec0ab69d0fda74588e: reading manifest fe77272021867cc6b6d5d0c9bd06c99d4024ad53f1ab94ec0ab69d0fda74588e in localhost:55000/3scale-amp2/system-rhel7: manifest unknown |
| 42 | +---- |
| 43 | + |
| 44 | +.. Check for warnings in the console or log file indicating which Operators are incomplete. |
| 45 | ++ |
| 46 | +If an Operator is flagged as incomplete, the image related to that Operator likely failed to mirror. |
| 47 | + |
| 48 | +.. Manually mirror the missing image or retry the mirroring process. |
| 49 | + |
| 50 | +. Check for errors related to generated cluster resources. Even if some images fail to mirror, oc-mirror v2 will still generate cluster resources such as `IDMS.yaml` and `ITMS.yaml` files for the successfully mirrored images. |
| 51 | +.. Check the output directory for the generated files. |
| 52 | +.. If these files are missing for specific images, ensure that no critical errors occurred for those images during the mirroring process. |
| 53 | + |
| 54 | +By following these steps, you can better diagnose issues and ensure smoother mirroring. |
0 commit comments