Project

General

Profile

Bug #32001

Publish of content view is aborted with Error "Validation failed: Relative path is too long (maximum is 255 characters)"

Added by Nadja Heitmann 8 months ago. Updated about 1 month ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Content Views
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

We wanted to publish a content view that contains a repository with a relatively long repo_label and got the message:

Result: the publish is aborted with the error message "Validation failed: Relative path is too long (maximum is 255 characters)"

The error seems to be caused by the nature of the `relative path`, that consists of several labels (e.g. product, repository, content view, etc). The relative path itself can be up to 255 characters, and the sub-components are allowed to be 255 characters as well. This might eventually clash.

A workaround is to alter the `katello_repositories` foreman db table manually, as well as the `cp2_content` candlepin table.

History

#1 Updated by Chris Roberts 8 months ago

  • Status changed from New to Need more information
  • Category set to Content Views

Hi Nadja,

Which version of Katello are you seeing this in?

#2 Updated by Nadja Heitmann 8 months ago

  • Found in Releases Katello 3.16.0 added

#3 Updated by Nadja Heitmann 8 months ago

  • Found in Releases Katello 3.18.0 added
  • Found in Releases deleted (Katello 3.16.0)

#4 Updated by Nadja Heitmann 8 months ago

I have tested this
  • on my local Forklift with Katello 3.18, Foreman 2.3
  • on a system with Katello 3.16, Foreman 2.1.3

I tried to test the same on the newest Forklift with centos7-katello-devel-stable, but it would give me an SSL error when I try to publish any content views (Katello 3.18, Foreman 2.4).

#5 Updated by James Jeffers 7 months ago

  • Triaged changed from No to Yes
  • Target version set to Katello 4.1.0

#6 Updated by Nadja Heitmann 7 months ago

Still any information missing? If yes, please let me know.

#7 Updated by Jonathon Turel 5 months ago

  • Target version changed from Katello 4.1.0 to Katello 4.2.0
  • Status changed from Need more information to New

#8 Updated by Justin Sherrill about 2 months ago

  • Triaged changed from Yes to No
  • Target version deleted (Katello 4.2.0)

#9 Updated by Samir Jha about 2 months ago

  • Triaged changed from No to Yes
  • Target version set to Katello Backlog

#10 Updated by Jonathon Turel about 1 month ago

I don't think the cp2_contsnts fields need an update since the label and url don't get constructed with the CV label or environment path. We definitely need to do something about relative_path for the katello_repositories though.

Food for thought: https://wiki.postgresql.org/wiki/Don%27t_Do_This#Don.27t_use_varchar.28n.29_by_default

Also available in: Atom PDF