Bug 2170177

Summary: Creating a content view with valid acceptable characters in Label fails with error "Validation failed: Label cannot contain characters other than ascii alpha numerals, '_', '-'."
Product: Red Hat Satellite Reporter: Jayant Bhatia <jbhatia>
Component: Content ViewsAssignee: Lucy Fu <lufu>
Status: POST --- QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: low Docs Contact:
Priority: low    
Version: 6.13.0CC: sajha
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
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: 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:

Description Jayant Bhatia 2023-02-15 19:38:49 UTC
Description of problem:

Content View creation fails with mentioned error even when the "Label" contain all the valid acceptable characters  


Version-Release number of selected component (if applicable): satellite-6.13.0-4.el8sat.noarch


How reproducible: Always


Steps to Reproduce:

1. Navigate to Satellite WebUI -> Content -> Content Views -> Create Content View.

2. Enter "Name" as "RHEL 8.7". The "Label" is automatically populated with following value: "RHEL_8_7". 

3. Click on 'Create Content View'.


Actual results: The content view creation fails with error:
 
       Validation failed: Label cannot contain characters other than ascii alpha numerals, '_', '-'."


Expected results: The content view should get successfully created as Label has valid acceptable characters.


Additional info: The issue is also reproducible on Satellite 6.12.

Comment 4 Bryan Kearney 2023-05-26 16:03:00 UTC
Upstream bug assigned to lufu

Comment 5 Bryan Kearney 2023-05-26 16:03:01 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/35235 has been resolved.