Skip to content

OCPBUGS#2892: Added known issue for IBM Cloud VPC #52820

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 6, 2022
Merged

OCPBUGS#2892: Added known issue for IBM Cloud VPC #52820

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
71 changes: 71 additions & 0 deletions release_notes/ocp-4-12-release-notes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1102,6 +1102,77 @@ This script removes unauthenticated subjects from the following cluster role bin
+
(link:https://bugzilla.redhat.com/show_bug.cgi?id=1821771[*BZ#1821771*])

// TODO: This known issue should be removed when RHCOS images begin using RHEL 9. RHEL 9 prevents this issue from occurring.
* Intermittently, an IBM Cloud VPC cluster might fail to install because some worker machines do not start. Rather, these worker machines remain in the `Provisioned` phase.
+
There is a workaround for this issue. From the host where you performed the initial installation, delete the failed machines and run the installation program again.
+
. Verify that the status of the internal application load balancer (ALB) for the master API server is `active`.
.. Identify the cluster's infrastructure ID by running the following command:
+
[source,terminal]
----
$ oc get infrastructure/cluster -ojson | jq -r '.status.infrastructureName'
----
.. Log into the IBM Cloud account for your cluster and target the correct region for your cluster.
.. Verify that the internal ALB status is `active` by running the following command:
+
Copy link

@MayXuQQ MayXuQQ Nov 24, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

get the cluster region
$oc get machines -n openshift-machine-api
...
set the target to the cluster
$ibmcloud target -g <cluster_ID> -r <cluster_region>

Copy link

@jeffnowicki jeffnowicki Nov 30, 2022 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@MayXuQQ I'd prefer to simplify your suggestion and state: "Before executing the following command, ensure you are logged into the IBM Cloud account for your cluster and target the correct region for your cluster." I think it's reasonable for the user to know how to log into ibmcloud and target the correct region (no need to give actual commands).

@mjpytlak Please insert the above sentence as follows:

Before executing the following command, ensure you are logged into the IBM Cloud account for your cluster and target the correct region for your cluster. Verify that the internal ALB status is active by running the following command:

[source,terminal]
----
$ ibmcloud is lb <cluster_ID>-kubernetes-api-private --output json | jq -r '.provisioning_status'
----
. Identify the machines that are in the `Provisioned` phase by running the following command:
+
[source,terminal]
----
$ oc get machine -n openshift-machine-api
----
+
.Example output
[source,terminal]
----
NAME PHASE TYPE REGION ZONE AGE
example-public-1-x4gpn-master-0 Running bx2-4x16 us-east us-east-1 23h
example-public-1-x4gpn-master-1 Running bx2-4x16 us-east us-east-2 23h
example-public-1-x4gpn-master-2 Running bx2-4x16 us-east us-east-3 23h
example-public-1-x4gpn-worker-1-xqzzm Running bx2-4x16 us-east us-east-1 22h
example-public-1-x4gpn-worker-2-vg9w6 Provisioned bx2-4x16 us-east us-east-2 22h
example-public-1-x4gpn-worker-3-2f7zd Provisioned bx2-4x16 us-east us-east-3 22h
----
. Delete each failed machine by running the following command:
+
[source,terminal]
----
$ oc delete machine <name_of_machine> -n openshift-machine-api
----
. Wait for the deleted worker machines to be replaced, which can take up to 10 minutes.
. Verify that the new worker machines are in the `Running` phase by running the following command:
+
[source,terminal]
----
$ oc get machine -n openshift-machine-api
----
+
.Example output
[source,terminal]
----
NAME PHASE TYPE REGION ZONE AGE
example-public-1-x4gpn-master-0 Running bx2-4x16 us-east us-east-1 23h
example-public-1-x4gpn-master-1 Running bx2-4x16 us-east us-east-2 23h
example-public-1-x4gpn-master-2 Running bx2-4x16 us-east us-east-3 23h
example-public-1-x4gpn-worker-1-xqzzm Running bx2-4x16 us-east us-east-1 23h
example-public-1-x4gpn-worker-2-mnlsz Running bx2-4x16 us-east us-east-2 8m2s
example-public-1-x4gpn-worker-3-7nz4q Running bx2-4x16 us-east us-east-3 7m24s
----
. Complete the installation by running the following command. Running the installation program again ensures that the cluster's `kubeconfig` is initialized properly:
+
[source,terminal]
----
$ ./openshift-install wait-for install-complete
----
+
(link:https://issues.redhat.com/browse/OCPBUGS-1327[*OCPBUGS#1327*])

Copy link
Contributor

@jeana-redhat jeana-redhat Dec 6, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
+
(link:https://issues.redhat.com/browse/OCPBUGS-1327[*OCPBUGS#1327*])

Copy link
Contributor Author

@mjpytlak mjpytlak Dec 6, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK. All set.

// TODO: This known issue should carry forward to 4.9 and beyond!
* The `oc annotate` command does not work for LDAP group names that contain an equal sign (`=`), because the command uses the equal sign as a delimiter between the annotation name and value. As a workaround, use `oc patch` or `oc edit` to add the annotation. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1917280[*BZ#1917280*])

Expand Down