Bug 1893629 - [Console>Internal-attached Devices>Step2:Create Storage Class]: Volume Set name should conform to the DNS label standards
Summary: [Console>Internal-attached Devices>Step2:Create Storage Class]: Volume Set n...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenShift Container Storage
Classification: Red Hat Storage
Component: management-console
Version: 4.6
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Nishanth Thomas
QA Contact: Elad
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-02 08:26 UTC by Santosh Pillai
Modified: 2020-11-02 09:14 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-02 09:14:49 UTC
Embargoed:


Attachments (Terms of Use)

Description Santosh Pillai 2020-11-02 08:26:25 UTC
Description of problem:
`Volume Set Name` field does not conform to the DNS label standards (https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#dns-label-names). So entering an invalid names leads to failure in LocalVolumeSet.

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

How reproducible:
Every time

Steps to Reproduce:
1.Install LSO 4.6 on OCP 4.6
2.Install OCS 4.6
3.In `Internal-attached Devices>Step2:Create Storage Class` enter `Volume Set Name` with caps, say `LOCALBLOCK`. 

Actual results:
LocalVolumeSet fails with error 
Error "Invalid value: "LOCALBLOCK": 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".


Expected results:
`Volume Set Name` field should conform to the DNS label standards 


Additional info:

Comment 3 Santosh Pillai 2020-11-02 09:14:49 UTC
The blocking message in the UI looks good. I hadn't seen it or missed it when I tested. Closing this issue.


Note You need to log in before you can comment on or make changes to this bug.