Skip to content

Commit 97b1615

Browse files
authored
Merge pull request #59230 from skopacz1/OCPBUGS-9238
2 parents b96b607 + 8fa927e commit 97b1615

File tree

2 files changed

+8
-6
lines changed

2 files changed

+8
-6
lines changed

modules/installation-mirror-repository.adoc

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -178,7 +178,7 @@ $ oc image mirror -a ${LOCAL_SECRET_JSON} --from-dir=${REMOVABLE_MEDIA_PATH}/mir
178178
+
179179
[IMPORTANT]
180180
====
181-
Running `oc image mirror` might result in the following error: `error: unable to retrieve source image`. This error occurs when image indexes include references to images that no longer exist on the image registry. Image indexes might retain older references to allow users running those images an upgrade path to newer points on the upgrade graph. As a temporary workaround, you can use the `--skip-missing` option to bypass the error and continue downloading the image index. For more information, see link:https://access.redhat.com/solutions/6975305[Service Mesh Operator mirroring failed].
181+
Running `oc image mirror` might result in the following error: `error: unable to retrieve source image`. This error occurs when image indexes include references to images that no longer exist on the image registry. Image indexes might retain older references to allow users running those images an upgrade path to newer points on the upgrade graph. As a temporary workaround, you can use the `--skip-missing` option to bypass the error and continue downloading the image index. For more information, see link:https://access.redhat.com/solutions/6975305[Service Mesh Operator mirroring failed].
182182
====
183183

184184
** If the local container registry is connected to the mirror host, take the following actions:
@@ -244,8 +244,6 @@ that you selected, you must extract the installation program from the mirrored
244244
content.
245245

246246
You must perform this step on a machine with an active internet connection.
247-
248-
If you are in a disconnected environment, use the `--image` flag as part of must-gather and point to the payload image.
249247
====
250248
+
251249
. For clusters using installer-provisioned infrastructure, run the following command:

modules/support-gather-data.adoc

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ You can gather debugging information about your cluster by using the `oc adm mus
2020

2121
[NOTE]
2222
====
23-
If your cluster is using a restricted network, you must take additional steps. If your mirror registry has a trusted CA, you must first add the trusted CA to the cluster. For all clusters on restricted networks, you must import the default `must-gather` image as an image stream.
23+
If your cluster is in a disconnected environment, you must take additional steps. If your mirror registry has a trusted CA, you must first add the trusted CA to the cluster. For all clusters in disconnected environments, you must import the default `must-gather` image as an image stream.
2424
2525
[source,terminal]
2626
----
@@ -36,13 +36,17 @@ $ oc import-image is/must-gather -n openshift
3636
$ oc adm must-gather
3737
----
3838
+
39-
39+
[IMPORTANT]
40+
====
41+
If you are in a disconnected environment, use the `--image` flag as part of must-gather and point to the payload image.
42+
====
43+
+
4044
[NOTE]
4145
====
4246
Because this command picks a random control plane node by default, the pod might be scheduled to a control plane node that is in the `NotReady` and `SchedulingDisabled` state.
4347
====
4448

45-
.. If this command fails, for example, if you cannot schedule a pod on your cluster, then use the `oc adm inspect` command to gather information for particular resources.
49+
.. If this command fails, for example, if you cannot schedule a pod on your cluster, then use the `oc adm inspect` command to gather information for particular resources.
4650
+
4751
[NOTE]
4852
====

0 commit comments

Comments
 (0)