Bug 2124275

Summary: Repository export fails with Error "Validation failed: Relative path is too long (maximum is 255 characters)"
Product: Red Hat Satellite Reporter: Yogendra <yyadav>
Component: Content ViewsAssignee: Chris Roberts <chrobert>
Status: POST --- QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.10.7CC: chrobert, iballou, paji, sajha
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: https://projects.theforeman.org/issues/36584
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 Yogendra 2022-09-05 13:38:54 UTC 
Description of problem:

Exporting repository gives error when Label name of repository and product has maximum character.

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

Red Hat Satellite 6.10.7

How reproducible:


Steps to Reproduce:

1. Create a product with long label name (For example: Community_Extra_Packages_for_Enterprise_Linux_EPEL_debug)

2. Create a repository with long label name (Fore example: Community_Extra_Packages_for_Enterprise_Linux_EPEL_8_Modular_x86_64_debug)

3. Sync the repository and then execute hammer command to  export repository.

Actual results:

Now we will faced the actual issue hammer command throws Error "Validation failed: Relative path is too long (maximum is 255 characters)" 

Expected results:

Repository export should be completed successfully.
Comment 1 Partha Aji 2023-04-06 23:28:50 UTC 
Changed component because this is related to Content View publishing rather than ISS

1. Create a product with long label name (For example: Community_Extra_Packages_for_Enterprise_Linux_EPEL_debug)

2. Create a repository with long label name (Fore example: Community_Extra_Packages_for_Enterprise_Linux_EPEL_8_Modular_x86_64_debug)

3. Sync the repository 

4. Create a content view with label along  Community_Extra_Packages_for_Enterprise_Linux_EPEL_8_Modular_x86_64_debug_100000

5. Publish

Actual results:

Error => "Validation failed: Relative path is too long (maximum is 255 characters)" 

Expected results:

Publish should be completed successfully.
Comment 2 Bryan Kearney 2023-07-17 16:02:30 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36584 has been resolved.