Skip to content

Commit 8dfe1c4

Browse files
Apply suggestions from code review
Co-authored-by: JoanneOFlynn2018 <45287002+JoanneOFlynn2018@users.noreply.github.com>
1 parent 1640074 commit 8dfe1c4

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

docs_user/modules/proc_updating-shiftstack-credentials.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@
77
After {rhos_long} adoption, any {rhocp_long} clusters that were deployed on {rhos_prev_long} ({OpenStackShort}) 17.1 with installer-provisioned infrastructure (Shift on Stack) still reference the {OpenStackPreviousInstaller} keystone endpoint in their cloud credentials. To authenticate with keystone and avoid timeouts, update the credentials and image-registry operator.
88

99
[IMPORTANT]
10-
Run all commands against the guest {OpenShiftShort} cluster (Shiftstack) that is running on {OpenStackShort} VMs, not the underlying {rhos_acro} host cluster.
10+
Run all commands against the guest {OpenShiftShort} cluster (Shiftstack) that is running on {OpenStackShort} instances, not the underlying {rhos_acro} host cluster.
1111

1212
.Procedure
1313

@@ -53,7 +53,7 @@ $ oc get secret installer-cloud-credentials -n openshift-image-registry \
5353
----
5454
+
5555
[NOTE]
56-
The output should show the new {rhos_acro} endpoint in the `auth_url` field. If the output still shows the previous endpoint after a few minutes, check that the CCO pod is running and that the CCO mode is Passthrough:
56+
The output should show the new {rhos_acro} endpoint in the `auth_url` field. If the output still shows the previous endpoint after a few minutes, check that the CCO pod is running and that the CCO mode is `Passthrough`:
5757
+
5858
----
5959
$ oc get pods -n openshift-cloud-credential-operator

0 commit comments

Comments
 (0)