Bug 2109193 - Power VS machine Processor is always defaulted to 0.5
Summary: Power VS machine Processor is always defaulted to 0.5
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Compute
Version: 4.12
Hardware: ppc64le
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.11.z
Assignee: Karthik K N
QA Contact: pdsilva
URL:
Whiteboard:
Depends On: 2107578
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-20 15:39 UTC by OpenShift BugZilla Robot
Modified: 2022-09-20 16:35 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-09-20 16:34:44 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift machine-api-operator pull 1041 0 None open [release-4.11] Bug 2109193: Fix while setting default processor value for Power VS platform 2022-07-20 15:40:06 UTC
Red Hat Product Errata RHSA-2022:6536 0 None None None 2022-09-20 16:35:00 UTC

Comment 1 Joel Speed 2022-08-08 15:08:57 UTC 
Waiting on 4.11 GA and QA to take a look at the dependent bug
Comment 4 pdsilva 2022-09-01 08:04:56 UTC 
Unable to verify this at the moment due to cluster deployment failures on Power VS.
Comment 7 pdsilva 2022-09-07 14:26:07 UTC 
Verification is still blocked due to cluster deployment failures in Power VS
Comment 9 pdsilva 2022-09-13 09:03:57 UTC 
Verified with 4.11.4. Successfully tested modifying the cpu/memory values.
Comment 12 errata-xmlrpc 2022-09-20 16:34:44 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.11.5 bug fix and 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.

https://access.redhat.com/errata/RHSA-2022:6536
Note You need to log in before you can comment on or make changes to this bug.