Bug 1741473

Summary: Create button on baremetal creation form should be in consistent style with other buttons
Product: OpenShift Container Platform Reporter: Yadan Pei <yapei>
Component: Console Metal3 PluginAssignee: Florian Fuchs <flfuchs>
Status: CLOSED ERRATA QA Contact: Udi Kalifon <ukalifon>
Severity: low Docs Contact:
Priority: medium    
Version: 4.2.0CC: aos-bugs, dkholodo, jtomasek, ncredi, yapei
Target Milestone: ---   
Target Release: 4.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-16 06:36:02 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
CreateButtonOnForm none

Description Yadan Pei 2019-08-15 09:15:17 UTC
Description of problem:
Create button on bare metal host creation form should be in consistent style with other buttons

Version-Release number of selected component (if applicable):
4.2.0-0.nightly-2019-08-14-211610

How reproducible:
Always

Steps to Reproduce:
1. Cluster admin goes to Compute -> Bare Metal Hosts -> Add Host

Actual results:
1. In baremetal host creation form, Create button is using different button style class="pf-c-button pf-m-primary btn btn-primary"

Expected results:
1. The button should be PF4 button and in consistent with 'Add Host'  class="pf-c-button pf-m-primary"

Additional info:

Comment 1 Yadan Pei 2019-08-15 09:16:14 UTC
Created attachment 1604029 [details]
CreateButtonOnForm

Comment 2 Jiri Tomasek 2019-08-15 16:46:48 UTC
There is an obsolete className specified on the Button. (className="btn btn-primary") this should be removed.

Comment 4 Danylo Kholodov 2019-08-29 12:02:51 UTC
Verified

Comment 5 errata-xmlrpc 2019-10-16 06:36:02 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