Bug 1820224

Summary: Backingstore creation dialog name field issues
Product: OpenShift Container Platform Reporter: Ben Eli <belimele>
Component: Console Storage PluginAssignee: Bipul Adhikari <badhikar>
Status: CLOSED DUPLICATE QA Contact: Raz Tamir <ratamir>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.5CC: aos-bugs, badhikar, jefbrown, madam, nbecker, nthomas, ocs-bugs
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1821609 (view as bug list) Environment:
Last Closed: 2020-04-07 16:49:55 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:
Bug Depends On:    
Bug Blocks: 1821609    

Description Ben Eli 2020-04-02 14:34:31 UTC
Description of problem (please be detailed as possible and provide log
snippests):
When creating a new backingstore via the UI, the 'name' field is marked with a red asterisk, but also states 'If not provided, a generic name will be generated'.

However, if a name isn't provided, and the user chooses to supply credentials (and not to pick an existing secret), and the user clicks on 'Create Backing Store', the user receives the following error:

"An error occurred
Error "Invalid value: "-secret": a DNS-1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')" for field "metadata.name"."

After clicking again, the error changes - 
"An error occurred
Error "Required value: name or generateName is required" for field "metadata.name"."

Also, please note that the field has a red asterisk, meaning it is mandatory - but also have a text implying that it's not...

Version of all relevant components (if applicable):
OCS 4.3.0-394.ci


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
No, it's possible to input a backingstore name to circumvent this

Is there any workaround available to the best of your knowledge?
Above.

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
1

Can this issue reproducible?
Yes

Can this issue reproduce from the UI?
Yes


Steps to Reproduce:
1. Go to the OpenShift management UI -> Operators -> Installed -> OCS -> Backing Store tab
2. 'Create new Backing Store'
3. Fill all the fields except the name (random data is enough), make sure to "Switch to Credentials"


Actual results:
Creation is blocked

Expected results:
Creation succeeds

Additional info:

Comment 4 Ben Eli 2020-04-07 16:49:55 UTC

*** This bug has been marked as a duplicate of bug 1819674 ***