Bug 1731801

Summary: Use correct style for Create button on Deployment Config page
Product: OpenShift Container Platform Reporter: Yadan Pei <yapei>
Component: Management ConsoleAssignee: Jakub Hadvig <jhadvig>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.2.0CC: aos-bugs, jhadvig, jokerman, mmccomas, yapei
Target Milestone: ---   
Target Release: 4.2.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-16 06:30:16 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:
Description Flags
CreateDeploymentConfigButton none

Description Yadan Pei 2019-07-22 06:29:28 UTC
Description of problem:

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

How reproducible:

Steps to Reproduce:
1. Users goes to Workloads -> Deployment Config, click Create

Actual results:
1. There is only one option `From YAML` but the Create button is using class="pf-c-dropdown__toggle pf-c-dropdown__toggle"

Expected results:
1. If only `From YAML` is applicable/can be selected then we should eliminate and only leave the button as `Create`, so that we can use the same css style with other workloads creation button(blue button) `class="pf-c-button pf-m-primary"`

Additional info:

Comment 1 Yadan Pei 2019-07-22 06:30:26 UTC
Created attachment 1592521 [details]

Comment 2 Yadan Pei 2019-07-22 06:30:48 UTC
Created attachment 1592522 [details]

Comment 3 Jakub Hadvig 2019-07-22 08:04:39 UTC
PR: https://github.com/openshift/console/pull/2110

Comment 5 Yadan Pei 2019-07-23 05:47:51 UTC
Create Deployment Config is now using correct class class="pf-c-button pf-m-primary"

Verified on 4.2.0-0.nightly-2019-07-23-002801

Comment 6 errata-xmlrpc 2019-10-16 06:30:16 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.