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

Bug 2024708

Summary: The form for creating operational CRs is badly rendering filed names ("obsoleteCPUs" -> "Obsolete CP Us" )
Product: OpenShift Container Platform Reporter: Simone Tiraboschi <stirabos>
Component: Management ConsoleAssignee: Jon Jackson <jonjacks>
Status: CLOSED ERRATA QA Contact: Xiyun Zhao <xiyuzhao>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.10CC: jhadvig, jonjacks, kmajcher, spadgett, yapei
Target Milestone: ---   
Target Release: 4.11.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-08-10 10:39:48 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:
Attachments:
Description Flags
Obsolete CP Us none

Description Simone Tiraboschi 2021-11-18 17:41:07 UTC
Created attachment 1842629 [details]
Obsolete CP Us

Description of problem:

On Openshift Virtualization CRD we have a field named "obsoleteCPUs" 

              obsoleteCPUs:
                description: ObsoleteCPUs allows avoiding scheduling of VMs for obsolete
                  CPU models


that is rendered as "Obsolete CP Us" on the auto generated UI form.

see the attached screenshot.



Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. Deploy Openshift Virtualization from redhat-operator catalog
2. try to create a CR from the autogenerated from
3. Look for "Obsolete C..."

Actual results:
"obsoleteCPUs" -> "Obsolete CP Us"

Expected results:
"obsoleteCPUs" -> "Obsolete CPUs"

Additional info:

Comment 1 Jon Jackson 2021-11-23 14:38:50 UTC
Did not get a chance to fix this sprint, will address in a future sprint.

Comment 4 Jon Jackson 2022-04-14 14:02:51 UTC
Hi Krzysztof, I still haven't been able to get around to this. I'll see if there's a quick fix I can get in soon.

Comment 7 Xiyun Zhao 2022-04-29 07:59:57 UTC
This bug has been verified on payload 4.11.0-0.nightly-2022-04-26-181148

Verification Step:
1. Install "Openshift Virtualization" from Operator -> OperatorHub page
2. Create CR for the operator by using the below list ways
   2.1 Click on "Create HyperConverged" (in Waring banner)on Operator Details -> Details Tab
   2.2 Click "Create instance" button on Provided API section for OpenShift Virtualization Deployment on Operator details -> Details Tab
3. Check the text of "obsoleteCPUs" on the "Create Hyperconverged" form page

Result
3. "Obsolete CP Us" is now updated to "obsoleteCPUs", the first letter is lowercase, and the space between P and U has been removed

Comment 10 errata-xmlrpc 2022-08-10 10:39:48 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