Bug 1740577

Summary: Bare Metal host page should check if maintenance action already started
Product: OpenShift Container Platform Reporter: Artem Hrechanychenko <ahrechan>
Component: Console Metal3 PluginAssignee: Jiri Tomasek <jtomasek>
Status: CLOSED DUPLICATE QA Contact: Udi Kalifon <ukalifon>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 4.2.0CC: aos-bugs
Target Milestone: ---   
Target Release: 4.2.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-13 14:33:47 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 Artem Hrechanychenko 2019-08-13 10:01:02 UTC
Description of problem:
From UI I request "Start Maintenance" action . Host status wasn't automatically changed to "Starting Maintenance" or "Under Maintenance" and I was able to request "Start Maintenance" again and provide different maintenance reasons. As result - many NMO object was created. All of them with different UUID

[cloud-user@rhhi-node-worker-0 dev-scripts]$ oc get nodemaintenances --all-namespaces
NAME AGE
nm-2jpm9 4m
nm-kfdng 2m54s
nm-xzq4k 3m24s
 [cloud-user@rhhi-node-worker-0 dev-scripts]$ oc describe nodemaintenance nm-kfdng --all-namespaces
Name: nm-kfdng
Namespace: 
Labels: <none>
Annotations: <none>
API Version: kubevirt.io/v1alpha1
Kind: NodeMaintenance
Metadata:
 Creation Timestamp: 2019-08-13T09:41:45Z
 Finalizers:
 foregroundDeleteNodeMaintenance
 Generate Name: nm-
 Generation: 1
 Resource Version: 55015
 Self Link: /apis/kubevirt.io/v1alpha1/nodemaintenances/nm-kfdng
 UID: 906062d1-bdae-11e9-b0bf-5254004e07e4
Spec:
 Node Name: rhhi-node-master-0
 Reason: test3
Events: <none>
 
[cloud-user@rhhi-node-worker-0 dev-scripts]$ oc describe nodemaintenance nm-2jpm9 --all-namespaces
Name: nm-2jpm9
Namespace: 
Labels: <none>
Annotations: <none>
API Version: kubevirt.io/v1alpha1
Kind: NodeMaintenance
Metadata:
 Creation Timestamp: 2019-08-13T09:40:39Z
 Finalizers:
 foregroundDeleteNodeMaintenance
 Generate Name: nm-
 Generation: 1
 Resource Version: 54460
 Self Link: /apis/kubevirt.io/v1alpha1/nodemaintenances/nm-2jpm9
 UID: 691c7845-bdae-11e9-b0bf-5254004e07e4
Spec:
 Node Name: rhhi-node-master-0
 Reason: test
Events: <none>

Version-Release number of selected component (if applicable):
registry.svc.ci.openshift.org/ocp/4.2-2019-07-31-123929@sha256:c8a69a3293c215194101108266f6eecd7806e7f9c3b6770302c0807292ae5c1a

How reproducible:
always

Steps to Reproduce:
1.Start maintenance from UI.  
2.Do not refresh page. Click to start maintenance again
3.Refresh page and stop maintenance.
4. refresh page and try to stop maintenance again

Actual results:
Several NMO object created. User cannot stop maintenance from UI

Expected results:
Only first request for Start Maintenance should proceed. All next should be blocked or page should automatically refreshed state after started maintenance 

Additional info:

Comment 1 Jiri Tomasek 2019-08-13 14:33:47 UTC

*** This bug has been marked as a duplicate of bug 1737756 ***