Bug 2221921

Summary: Bootable volumes page - title mismatch
Product: Container Native Virtualization (CNV) Reporter: Avital Pinnick <apinnick>
Component: User ExperienceAssignee: Hilda Stastna <hstastna>
Status: CLOSED ERRATA QA Contact: Guohua Ouyang <gouyang>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.14.0CC: gouyang, hstastna, rsdeor, yfrimanm
Target Milestone: ---   
Target Release: 4.14.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-11-08 14:05:53 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
Bootable volumes page title mismatch none

Description Avital Pinnick 2023-07-11 09:41:29 UTC
Created attachment 1975112 [details]
Bootable volumes page title mismatch

"Bootable volumes" appears in the main navigation but the page is called "Bootable resources".

Comment 1 Hilda Stastna 2023-07-11 11:43:43 UTC
Hi,

what do you suggest to rename? page title or the navigation title? Thanks!

Comment 2 Avital Pinnick 2023-07-11 12:42:27 UTC
(In reply to Hilda Stastna from comment #1)
> Hi,
> 
> what do you suggest to rename? page title or the navigation title? Thanks!

I think your team can decide.

Comment 3 Yifat Menchik 2023-07-11 12:49:39 UTC
 @hstastna TMO we should stick with "Bootable volumes". Thanks.

Comment 4 Yifat Menchik 2023-07-11 12:49:53 UTC
 @hstastna TMO we should stick with "Bootable volumes". Thanks.

Comment 5 Hilda Stastna 2023-07-11 13:45:13 UTC
Hi Yifat

I got some info that the page was renamed to "Bootable resources", the related doc:
https://docs.google.com/document/d/1oETHC4UpRnEGFEdiezUxMLzpQagWXOYz0DBYro-XHB0/
The doc was related to the feature: https://issues.redhat.com/browse/CNV-26881
WDYT? Do we want to stick to "volumes" anyway? Thanks!

Comment 6 Yifat Menchik 2023-07-18 11:13:08 UTC
Yes. For consistency reasons I think we should stick to Volumes. All instances in this doc should have been updated to "Bootable volumes" instead of "Bootable resources" because throughout the create VM from InstanceType flow we use the term "Volume" and not resource.
cc @rsdeor

Comment 7 Guohua Ouyang 2023-07-25 03:27:23 UTC
verified on kubevirt-console-plugin-rhel9:v4.14.0-2246

Comment 9 Ronen 2023-07-26 08:25:58 UTC
It looks like all open questions were resolved

Comment 10 errata-xmlrpc 2023-11-08 14:05:53 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 Virtualization 4.14.0 Images security and bug fix 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:6817