Bug 2045916 - [IBMCloud] Default machine profile in installer is unreliable
Summary: [IBMCloud] Default machine profile in installer is unreliable
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.0
Assignee: aos-install
QA Contact: Pedro Amoedo
: 2039965 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2022-01-25 23:08 UTC by Christopher J Schaefer
Modified: 2022-03-10 16:42 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-03-10 16:42:23 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift installer pull 5578 0 None Merged Bug 2045916: IBMCloud: Stop defaulting to dedicated storage profile 2022-02-01 14:52:25 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:42:39 UTC

Description Christopher J Schaefer 2022-01-25 23:08:47 UTC


Please specify:

What happened?

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.

Comment 1 Christopher J Schaefer 2022-01-25 23:11:59 UTC
Opened a PR to switch to a more reliable VSI profile

Comment 3 Pedro Amoedo 2022-01-28 10:23:27 UTC
*** Bug 2039965 has been marked as a duplicate of this bug. ***

Comment 7 errata-xmlrpc 2022-03-10 16:42:23 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.