Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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 1581628

Summary:	255 character length too short for content view names
Product:	Red Hat Satellite	Reporter:	Peter Ondrejka <pondrejk>
Component:	Content Views	Assignee:	Justin Sherrill <jsherril>
Status:	CLOSED WONTFIX	QA Contact:	Lai <ltran>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.3.1	CC:	bbuckingham, bkearney, egolov, jalberts, jcallaha, jeff_m_johnson, jotodd, jsherril, ktordeur, mhrivnak, pmoravec, pondrejk, tasander, vijsingh
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1365312	Environment:
Last Closed:	2020-02-03 16:29:54 UTC	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:
Bug Depends On:	1365312
Bug Blocks:

Comment 1 Pavel Moravec 2018-05-23 09:44:32 UTC

I see 6.3 creates shorter pulp repo names where the longest part (repo name from CDN) is replaced by UUID, like:

1-cv_capsule-v1_0-9c2f5684-357e-48c1-aab3-f24a153733a2

( organizationID-CVname-CVversion-baseRepoID format)

I understand that if a user provides a long CV name (longer than 211 chars), then the above string is >255chars long and the same underlying error happens.

My understanding is the original bug was not completely fixed, but I dont see why this is a regression..?

Comment 2 Satellite Program 2018-05-23 10:16:34 UTC

Upstream bug assigned to jsherril

Comment 3 Satellite Program 2018-05-23 10:16:40 UTC

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/17949 has been resolved.

Comment 4 Peter Ondrejka 2018-05-23 11:10:28 UTC

Removing the regression keyword, my impression was that the previous fix changed the way CV names were collected from sat UI.

Currently the robottelo automation tests this by supplying a long CV name, failure of the test made me think of this as of a regression.

Comment 5 Brad Buckingham 2018-05-29 17:46:32 UTC

Hi Peter,

Is this a bug or is this a case of the test needing to be updated for the new behavior?

Comment 6 Peter Ondrejka 2018-06-12 10:09:41 UTC

Brad, yes this is a bug, you need a CV with name longer than 211 characters and some synced content. CV publish in such case fails.

Comment 9 Bryan Kearney 2020-01-15 21:00:50 UTC

The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.

Comment 10 Bryan Kearney 2020-02-03 16:29:54 UTC

Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.