Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2124275 - Repository export fails with Error "Validation failed: Relative path is too long (maximum is 255 characters)"
Summary: Repository export fails with Error "Validation failed: Relative path is too...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.10.7
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: 6.15.0
Assignee: Chris Roberts
QA Contact: David Moore
URL: https://projects.theforeman.org/issue...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-05 13:38 UTC by Yogendra
Modified: 2024-11-08 07:49 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-04-23 17:12:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 36584 0 Normal Closed Repository export fails with Error "Validation failed: Relative path is too long 2023-09-07 14:11:20 UTC
Github Katello katello pull 10642 0 None open Fixes #36584 - Update realtive_path to text in the db from char 2023-07-12 15:22:12 UTC
Red Hat Issue Tracker SAT-18290 0 None None None 2023-06-12 16:37:09 UTC
Red Hat Knowledge Base (Solution) 6977334 0 None None None 2022-09-27 13:00:40 UTC
Red Hat Product Errata RHSA-2024:2010 0 None None None 2024-04-23 17:12:35 UTC

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.
Comment 4 Chris Roberts 2023-10-09 19:15:03 UTC 
What are the testing steps for this pull request?
Create a product with long label name (For example: Community_Extra_Packages_for_Enterprise_Linux_EPEL_debug)
Create a repository with long label name (Fore example: Community_Extra_Packages_for_Enterprise_Linux_EPEL_8_Modular_x86_64_debug)
Sync the repository
Create a content view with label along Community_Extra_Packages_for_Enterprise_Linux_EPEL_8_Modular_x86_64_debug_100000
Publish
Comment 5 Brad Buckingham 2023-10-30 11:29:29 UTC 
Bulk setting Target Milestone = 6.15.0 where sat-6.15.0+ is set.
Comment 9 errata-xmlrpc 2024-04-23 17:12:33 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 (Important: Satellite 6.15.0 release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2024:2010
Note You need to log in before you can comment on or make changes to this bug.