Bug 1741176

Summary:	Maintenance process should be driven by NodeMaintenance status
Product:	OpenShift Container Platform	Reporter:	Jiri Tomasek <jtomasek>
Component:	Console Metal3 Plugin	Assignee:	Jiri Tomasek <jtomasek>
Status:	CLOSED ERRATA	QA Contact:	Udi Kalifon <ukalifon>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.2.0	CC:	ahrechan, aos-bugs
Target Milestone:	---
Target Release:	4.2.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:	2019-10-16 06:35:55 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 Jiri Tomasek 2019-08-14 12:37:45 UTC

Description of problem:
Node maintenance is not a quick process, UI should track the maintenance process including transitional states (Starting maintenance -> under maintenance -> stopping maintenance)

Host actions restrictions need to get updated to take transitional maintenance states into account

In case of error state, UI should show the last error message in status popover.

Comment 2 Artem Hrechanychenko 2019-09-12 12:55:34 UTC

VERIFIED

Comment 3 errata-xmlrpc 2019-10-16 06:35:55 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/RHBA-2019:2922