Bug 2175979 - "Cores" should be "CPU" in instanceTypes page
Summary: "Cores" should be "CPU" in instanceTypes page
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: User Experience
Version: 4.13.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.13.0
Assignee: Phillip Bailey
QA Contact: Guohua Ouyang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-07 02:22 UTC by Guohua Ouyang
Modified: 2023-09-19 04:34 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-18 02:58:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CNV-26587 0 None None None 2023-03-07 02:23:34 UTC
Red Hat Product Errata RHSA-2023:3205 0 None None None 2023-05-18 02:58:14 UTC

Description Guohua Ouyang 2023-03-07 02:22:31 UTC
Description of problem:
"Cores" should be "CPU" in instanceTypes page, currently, it's "1 Cores, 4 GiB Memory" and "1 Cores | 4 GiB Memory".

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Guohua Ouyang 2023-03-07 02:23:23 UTC
Fabian, we want your opinion on this one.

Comment 3 errata-xmlrpc 2023-05-18 02:58:08 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 Virtualization 4.13.0 Images security, bug fix, and enhancement 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-2023:3205

Comment 4 Red Hat Bugzilla 2023-09-19 04:34:18 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days


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