Bug 1704220

Summary:	Stopping maintenance mode on node doesn't require confirmation
Product:	Container Native Virtualization (CNV)	Reporter:	Radim Hrazdil <rhrazdil>
Component:	User Experience	Assignee:	Rastislav Wagner <rawagner>
Status:	CLOSED ERRATA	QA Contact:	Radim Hrazdil <rhrazdil>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	2.0	CC:	cnv-qe-bugs, mgoldboi, ncredi, sgordon, tjelinek
Target Milestone:	---
Target Release:	2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	2.0.0-14.4	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-07-24 20:15:51 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:

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