Bug 1740569 - Bare Metal host page should check if stop maintenance action already started
Summary: Bare Metal host page should check if stop maintenance action already started
Keywords:
Status: CLOSED DUPLICATE of bug 1737756
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Metal3 Plugin
Version: 4.2.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: 4.2.0
Assignee: Jiri Tomasek
QA Contact: Udi Kalifon
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-13 09:39 UTC by Artem Hrechanychenko
Modified: 2019-09-07 10:20 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-13 14:32:22 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
screenshot (60.30 KB, image/png)
2019-08-13 09:39 UTC, Artem Hrechanychenko 		no flags Details
View All

Description Artem Hrechanychenko 2019-08-13 09:39:24 UTC 
Created attachment 1603258 [details]
screenshot

Description of problem:
From UI I request "Stop Maintenance action" . Host status wasn't automatically changed to "Under Maintenance" or "Stopping Maintenance" and I was able to request "Stop Maintenance" again and got next issue

"An error occurred
nodemaintenances.kubevirt.io "nm-m55fm" not found"

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 action
2.Wait until status changed to Under maintenance
3.Stop maintenance. do not refresh page. click start maintenance again

Actual results:

"An error occurred
nodemaintenances.kubevirt.io "nm-m55fm" not found"

Expected results:
Ui should block that action with notification that "stopping" in action

Additional info:
Comment 1 Jiri Tomasek 2019-08-13 14:32:22 UTC 

*** This bug has been marked as a duplicate of bug 1737756 ***
Note You need to log in before you can comment on or make changes to this bug.