Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2097239

Summary:	Change Lower CPU limits for Power VS cloud
Product:	OpenShift Container Platform	Reporter:	Basheer <bkhadars>
Component:	Installer	Assignee:	Nobody <nobody>
Installer sub component:	openshift-installer	QA Contact:	Julie <mjulie>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	unspecified	CC:	cnorman, mkumatag
Version:	4.11
Target Milestone:	---
Target Release:	4.11.0
Hardware:	ppc64le
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-08-10 11:17:59 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Basheer 2022-06-15 09:21:06 UTC

Thanks for opening a bug report!
Before hitting the button, please fill in as much of the template below as you can.
If you leave out information, it's harder to help you.
Be ready for follow-up questions, and please respond in a timely manner.
If we can't reproduce a bug we might close your issue.
If we're wrong, PLEASE feel free to reopen it and explain why.

Version:

$ openshift-install version
<your output here>

Platform:

#ppc64le

Please specify:
* IPI (automated install with `openshift-install`. If you don't know, then it's IPI)

What happened?

#To change lower limits of vcpu in powervs cloud

#See the troubleshooting documentation (https://github.com/openshift/installer/blob/master/docs/user/troubleshooting.md) for ideas about what information to collect.

#For example,

# If the installer fails to create resources (https://github.com/openshift/installer/blob/master/docs/user/troubleshooting.md#installer-fails-to-create-resources), attach the relevant portions of your `.openshift_install.log.`
# If the installer fails to bootstrap the cluster (https://github.com/openshift/installer/blob/master/docs/user/troubleshootingbootstrap.md), attach the bootstrap log bundle.
# If the installer fails to complete installation after bootstrapping completes (https://github.com/openshift/installer/blob/master/docs/user/troubleshooting.md#installer-fails-to-initialize-the-cluster), attach the must-gather log bundle using `oc adm must-gather`

# Always at least include the `.openshift_install.log`

What did you expect to happen?

#Enter text here.

How to reproduce it (as minimally and precisely as possible)?

$ your-commands-here

Anything else we need to know?

#Enter text here.

Comment 2 Julie 2022-06-21 11:11:35 UTC

No new nightly builds are available after 16th June, for verifying the fix.
Latest is dated 06-16 (https://mirror.openshift.com/pub/openshift-v4/ppc64le/clients/ocp-dev-preview/4.11.0-0.nightly-ppc64le-2022-06-16-003709)

Comment 4 Julie 2022-06-22 17:16:19 UTC

Verified with this build- 4.11.0-0.nightly-ppc64le-2022-06-21-133338

Tried specifying a value less than 0.5 for processors, in the install-config.yaml file (as shown below) which resulted in failure. This is the expected behavior.


compute:
- architecture: ppc64le
  hyperthreading: Enabled
  name: worker
  platform:
    powervs:
      sysType: e980
      processors: "0.1"
  replicas: 3

[root@mjul-rhl85-x1 june22]# ./openshift-install create manifests --dir 411-06-21
ERROR failed to fetch Master Machines: failed to load asset "Install Config": failed to create install config: invalid "install-config.yaml" file: [compute[0].platform.powervs.processors: Invalid value: 0.1: number of processors must be from .5 to 32 cores, compute[0].platform.powervs.processors: Invalid value: 0.1: processors must be in increments of .25]

Comment 7 errata-xmlrpc 2022-08-10 11:17:59 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 (Important: OpenShift Container Platform 4.11.0 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:5069