Project

General

Profile

Actions
Copy link

Bug #32001

open

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

Added by Nadja Heitmann about 3 years ago. Updated over 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Content Views
Target version:
Katello Backlog
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Katello 3.18.0
Red Hat JIRA:

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.

Actions
Copy link
 #1

Updated by Chris Roberts about 3 years ago

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

Hi Nadja,

Which version of Katello are you seeing this in?

Actions
Copy link
 #2

Updated by Nadja Heitmann about 3 years ago

  • Found in Releases Katello 3.16.0 added
Actions
Copy link
 #3

Updated by Nadja Heitmann about 3 years ago

  • Found in Releases Katello 3.18.0 added
  • Found in Releases deleted (Katello 3.16.0)
Actions
Copy link
 #4

Updated by Nadja Heitmann about 3 years 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).

Actions
Copy link
 #5

Updated by James Jeffers about 3 years ago

  • Target version set to Katello 4.1.0
  • Triaged changed from No to Yes
Actions
Copy link
 #6

Updated by Nadja Heitmann about 3 years ago

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

Actions
Copy link
 #7

Updated by Jonathon Turel almost 3 years ago

  • Status changed from Need more information to New
  • Target version changed from Katello 4.1.0 to Katello 4.2.0
Actions
Copy link
 #8

Updated by Justin Sherrill over 2 years ago

  • Target version deleted (Katello 4.2.0)
  • Triaged changed from Yes to No
Actions
Copy link
 #9

Updated by Samir Jha over 2 years ago

  • Target version set to Katello Backlog
  • Triaged changed from No to Yes
Actions
Copy link
 #10

Updated by Jonathon Turel over 2 years 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

Actions
Copy link

Also available in: Atom PDF