Bug 1819614

Summary: [IPI on BM] A space is needed when showing metal3 activities
Product: OpenShift Container Platform Reporter: Yadan Pei <yapei>
Component: Console Metal3 PluginAssignee: Yadan Pei <yapei>
Status: CLOSED ERRATA QA Contact: Udi Kalifon <ukalifon>
Severity: low Docs Contact:
Priority: low    
Version: 4.4CC: aos-bugs, dtaylor, jokerman, yapei
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Added space between activity name and Bare Metal Host resource link
 Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:24:43 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:
Attachments:
Description Flags
Activity Message none

Description Yadan Pei 2020-04-01 07:56:25 UTC 
Description of problem:
Power on and Power off bare metal hosts, there is message shown in `Ongoing` events, Powering on/off<BMH_name_with_link_to_node>, we need a space between message 'Powering on/off' and bare metal hosts name

Version-Release number of selected component (if applicable):
4.4.0-0.nightly-2020-03-31-053841

How reproducible:
Always

Steps to Reproduce:
1. Install IPI on BM cluster, power off and power on one bare metal hosts
2. check status on cluster Dashboard 


Actual results:
2. Show message with format Powering on/off<BMH_name_with_link_to_node>, see screenshot

Expected results:
2. We should add a space then it will become:
Powering on/off <BMH_name_with_link_to_node>
to be consistent with other events 

Additional info:
Comment 4 Yadan Pei 2020-06-17 03:15:08 UTC 
Created attachment 1697730 [details]
Activity Message

Now it shows message like: Powering on/off <link_to_bmh>

Verified on 4.5.0-0.nightly-2020-06-11-183238
Comment 6 errata-xmlrpc 2020-07-13 17:24:43 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:2409