Bug 2175976

Summary: "Select InstanceType" should show the volume's default instanceType
Product: Container Native Virtualization (CNV) Reporter: Guohua Ouyang <gouyang>
Component: User ExperienceAssignee: Aviv Turgeman <aturgema>
Status: CLOSED ERRATA QA Contact: Guohua Ouyang <gouyang>
Severity: high Docs Contact:
Priority: high    
Version: 4.13.0CC: fdeutsch, gouyang
Target Milestone: ---   
Target Release: 4.13.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-05-18 02:58:08 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
no default instancetype none

Description Guohua Ouyang 2023-03-07 02:13:56 UTC
Created attachment 1948597 [details]
no default instancetype

Description of problem:
While adding a volume, user can set the default instanceType.
If the volume is selected in the step "Select volume to boot from", the default value should be showing in "Select InstanceType", so user don't have to set it again unless user want to change the value.

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


How reproducible:


Steps to Reproduce:
1. Add a volume and set default instanceType
2. Select this volume
3.

Actual results:
No instanceType is selected at step 2 "Select InstanceType"

Expected results:
The default instanceType of the volume is selected in step 2.

Additional info:

Comment 1 Aviv Turgeman 2023-03-08 10:33:03 UTC
Hi @gouyang 

by UX design, the default instancetype should not be shown for now, probably will change
The current issue with this is that we show a set of common instance types to choose from, but there could be more instancetype to choose from,

I suggest showing the default instancetype selected in the VM details section, as for now it only shows the selected instancetype from step 2 and won't show the default one

Comment 2 Guohua Ouyang 2023-03-08 10:52:13 UTC
(In reply to Aviv Turgeman from comment #1)
> Hi @gouyang 
> 
> by UX design, the default instancetype should not be shown for now, probably
> will change

We can defer the issue to 4.14 then.

> The current issue with this is that we show a set of common instance types
> to choose from, but there could be more instancetype to choose from,
> 
> I suggest showing the default instancetype selected in the VM details
> section, as for now it only shows the selected instancetype from step 2 and
> won't show the default one

I think it's not necessary to show the default instancetype selected in the VM details because user has to select instancetype at step 2 since it's a must step.

The issue here is if it cannot show default instancetype at step 2, then there is no value to set the volume's default instancetype while adding it.

Comment 3 Aviv Turgeman 2023-03-08 11:46:09 UTC
(In reply to Guohua Ouyang from comment #2)
> (In reply to Aviv Turgeman from comment #1)
> > Hi @gouyang 
> > 
> > by UX design, the default instancetype should not be shown for now, probably
> > will change
> 
> We can defer the issue to 4.14 then.
> 
> > The current issue with this is that we show a set of common instance types
> > to choose from, but there could be more instancetype to choose from,
> > 
> > I suggest showing the default instancetype selected in the VM details
> > section, as for now it only shows the selected instancetype from step 2 and
> > won't show the default one
> 
> I think it's not necessary to show the default instancetype selected in the
> VM details because user has to select instancetype at step 2 since it's a
> must step.
> 
> The issue here is if it cannot show default instancetype at step 2, then
> there is no value to set the volume's default instancetype while adding it.

can you please defer this issue to 4.14? then we can ask UX to properly design a solution to this issue

Comment 5 Fabian Deutsch 2023-03-14 10:08:56 UTC
If a default IT is not presented as a tile then

today we can silently ignore it - after all it is just a default
today we could change our DataCronImports to not use highperformance and server ITs

in future we can have a design to introduce how custom instance types (which we can highperformance and server to be) to be shown in the create flow, but to me this is nothing we need right now.

Comment 7 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