Bug 1698474 - cancelled changes to VM flavor are saved for next edit
Summary: cancelled changes to VM flavor are saved for next edit
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: User Experience
Version: 2.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 2.0
Assignee: Phillip Bailey
QA Contact: Guohua Ouyang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-10 12:42 UTC by Guohua Ouyang
Modified: 2019-07-24 20:16 UTC (History)
6 users (show)

Fixed In Version: v2.0.0-14.2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-24 20:15:51 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt web-ui-components pull 396 0 None None None 2019-04-22 21:33:55 UTC
Red Hat Product Errata RHEA-2019:1850 0 None None None 2019-07-24 20:15:59 UTC

Description Guohua Ouyang 2019-04-10 12:42:57 UTC
Description of problem:
Edit VM flavor and type some different values, cancel and edit again, the values are not coming from vm's flavor, the values are from the last unsaved changes.

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

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Phillip Bailey 2019-04-18 12:01:09 UTC
Guohua,

I'm not able to reproduce this issue, but want to make sure I'm clear on the steps you're taking as "cancel and edit again" could be interpreted to mean two different procedures:

Procedure 1:

1. Open create VM wizard
2. Change Flavor to Custom
3. Enter values into the Memory and CPUs fields
4. Click the Cancel button
5. Repeat steps 1 and 2

Procedure 2:

1. Open create VM wizard
2. Change Flavor to Custom
3. Enter values into the Memory and CPUs fields
4. Change Flavor to any value other than Custom
5. Change Flavor back to Custom


If you mean Procedure 1, then this issue appears to have been fixed already as the values aren't repopulated. If you mean Procedure 2, I believe that it's intended for previously entered values to still be populated, but I could be wrong and we can get some clarification.

Could you please advise which procedure you mean?

Comment 2 Guohua Ouyang 2019-04-18 12:43:38 UTC
I was meaning Procedure 1 but not on wizard, on vm overview.
1. Open create VM overview
2. Change Flavor to Custom, the values are 1, 2
3. Enter values into the Memory and CPUs fields: 6, 8
4. Click the Cancel button, the flavor displayed 1 CPU, 2G Memory
5. Click the edit button, it's custom with values 6, 8.

At step5, it should be values 1, 2.

Comment 3 Phillip Bailey 2019-04-18 12:45:06 UTC
Ah, ok. I misunderstood. Thanks for the clarification!

Comment 4 Guohua Ouyang 2019-05-07 23:32:57 UTC
it's fixed in 2.0.0-14.2

Comment 6 errata-xmlrpc 2019-07-24 20:15:51 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, 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/RHEA-2019:1850


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