Bug 1737901 - Stop maintenance modal window show nmo name and name of node instead of bare metal host name
Summary: Stop maintenance modal window show nmo name and name of node instead of bare ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Metal3 Plugin
Version: unspecified
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ---
: 4.2.0
Assignee: Jiri Tomasek
QA Contact: Udi Kalifon
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-06 11:28 UTC by Artem Hrechanychenko
Modified: 2019-10-16 06:35 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-16 06:34:52 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
screenshot (10.34 KB, image/png)
2019-08-06 11:28 UTC, Artem Hrechanychenko 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 2354 0 None None None 2019-08-14 13:02:59 UTC
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:35:01 UTC

Description Artem Hrechanychenko 2019-08-06 11:28:16 UTC 
Created attachment 1600952 [details]
screenshot

Description of problem:
After click "stop maintenance" for Bare metal host object - modal window show nodemaintenance object name and name of k8s node instead of bare metal host name


Version-Release number of selected component (if applicable):
4.2.0-0.okd-2019-08-05-123143

How reproducible:
alway

Steps to Reproduce:
1.Deploy RHHI cluster using dev scripts
2.Start maintenance for bare metal node
3.Stop maintenance for bare metal node

Actual results:
- name of maintenance object 
- name of node


Expected results:
name of bare metal host
no info about maintenance object name or etc

Additional info:
Comment 2 Artem Hrechanychenko 2019-09-12 12:54:28 UTC 
VERIFIED
Comment 3 errata-xmlrpc 2019-10-16 06:34:52 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
Note You need to log in before you can comment on or make changes to this bug.