Bug 1770757

Summary: Node maintenance percentage is incorrectly calculated when NMO isn't running
Product: OpenShift Container Platform Reporter: Jiri Tomasek <jtomasek>
Component: Console Metal3 PluginAssignee: Jiri Tomasek <jtomasek>
Status: CLOSED ERRATA QA Contact: Udi Kalifon <ukalifon>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.3.0CC: aos-bugs, cvultur
Target Milestone: ---   
Target Release: 4.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
When Node Maintenance Operator is not running and maintenance is started, the UI now correctly shows 0% progress.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2020-01-23 11:12:05 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-11-11 10:02:35 UTC 
Description of problem:
Node maintenance percentage is incorrectly calculated when NMO isn't running or hasn't touched the maintenance CR yet.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. While NMO is not running, in 'Bare Metal Hosts' section select one of the hosts and run 'Start node maintenance' action from the kebab action menu.
2. Click 'Starting maintenance' host status to show popover

Actual results:
Popover shows 100% maintenance progress

Expected results:
Popover shows 0% maintenance progress


Additional info:
Comment 5 errata-xmlrpc 2020-01-23 11:12:05 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