Bug 1704220 - Stopping maintenance mode on node doesn't require confirmation
Summary: Stopping maintenance mode on node doesn't require confirmation
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: User Experience
Version: 2.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 2.0
Assignee: Rastislav Wagner
QA Contact: Radim Hrazdil
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-29 11:26 UTC by Radim Hrazdil
Modified: 2019-07-24 20:16 UTC (History)
5 users (show)

Fixed In Version: 2.0.0-14.4
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
Red Hat Product Errata RHEA-2019:1850 0 None None None 2019-07-24 20:15:59 UTC

Description Radim Hrazdil 2019-04-29 11:26:14 UTC 
Description of problem:
Stopping maintenance mode of a node doesn't show up the confirmation dialog which feels somewhat inconsistent with other VM/Node actions.

Especially when the current status of a node is not displayed on the node detail page, so user doesn't know whether anything happened or not.

Version-Release number of selected component (if applicable):
kubevirt-web-ui:v2.0.0-13

How reproducible:
100%

Steps to Reproduce:
1.
2. 
3.

Actual results:


Expected results:


Additional info:
Comment 1 Stephen Gordon 2019-05-01 20:47:09 UTC 
Not sure this is critical for CNV 2.0, will pm_ack+ for now but consider as nice to have depending on capacity.
Comment 2 Rastislav Wagner 2019-05-04 08:54:42 UTC 
https://github.com/kubevirt/web-ui/pull/357
Comment 3 Rastislav Wagner 2019-05-09 07:28:52 UTC 
https://github.com/kubevirt/web-ui/pull/365
Comment 4 Radim Hrazdil 2019-05-21 12:23:01 UTC 
Verified that Cancel Maintenance action needs to be confirmed
Version 2.0.0-14.5
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.