VSI's using the default IBM Cloud profile fail to provision and break IPI cluster creation, as VSI's get stuck in "Starting"
The default machine profile for IBM Cloud, bx2d-4x16, uses additional dedicated storage. However, this profile is known to be very unstable, and frequently results in failed VSI deployments when the storage cannot be allocated.
What did you expect to happen?
Successful IPI creation using the default IBM Cloud machine profile
How to reproduce it (as minimally and precisely as possible)?
Create a new IPI cluster using the default IBM Cloud profile (not specifying a profile in install-config)
One of more VSI's will likely be stuck in Starting waiting for block storage allocation, which cannot be provisioned
Anything else we need to know?
IBM Cloud is creating a PR to change the default profile to one without this dedicated storage, which has shown to be unreliable.
Opened a PR to switch to a more reliable VSI profile
*** Bug 2039965 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.