Bug 1757110 - When marking a node as schedulabe again, the baremetal hosts page still shows "starting maintenance"
Summary: When marking a node as schedulabe again, the baremetal hosts page still shows...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Metal3 Plugin
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.3.0
Assignee: Jiri Tomasek
QA Contact: Udi Kalifon
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-30 15:08 UTC by Udi Kalifon
Modified: 2020-05-13 21:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-13 21:26:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 3352 0 'None' 'open' 'Bug 1757110: Don''t allow to set Node schedulable when it is in maintenance' 2019-11-19 14:14:34 UTC
Red Hat Product Errata RHBA-2020:0062 0 None None None 2020-05-13 21:26:09 UTC

Description Udi Kalifon 2019-09-30 15:08:30 UTC
Description of problem:
The hosts page seems to not get updated when a node is marked as schedulable again from the node's details page


Steps to Reproduce:
1. From the baremetal hosts page, start a maintenance on one of the nodes
2. From the details page of the corresponding node, from the Actions pull-down, select "mark as schedulable"
3. Check back in the baremetal hosts page


Actual results:
Still in "starting maintenance"

Comment 1 Jason E. Rist 2019-11-06 15:18:50 UTC
When the node is in maintenance, UI should make the dropdown not allowed to be "mark as schedulable" (OR, remove Mark as Schedulable" from the UI)

Comment 3 Udi Kalifon 2019-11-20 08:15:11 UTC
Verified with a locally running console from 2019-11-20 and cluster version 4.3.0-0.ci-2019-11-19-095016

Comment 5 errata-xmlrpc 2020-05-13 21:26:07 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-2020:0062


Note You need to log in before you can comment on or make changes to this bug.