Bug 1424689 – Docker upstream repository name length limit

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1424689 - Docker upstream repository name length limit

Summary:	Docker upstream repository name length limit

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Satellite 6
Classification:	Red Hat
Component:	Repositories (Show other bugs)
Sub Component:
Version:	6.2.7
Hardware:	x86_64 Linux

Priority	high Severity high (vote)
Target Milestone:	6.2.14
Target Release:	Unused
Assigned To:	Tom McKay
QA Contact:	Jitendra Yejare
Docs Contact:

URL:
Whiteboard:
Keywords:	Triaged

Duplicates:	1484405 (view as bug list)
Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2017-02-18 03:25 EST by Preetesh Sharma
Modified:	2018-05-09 15:54 EDT (History)
CC List:	10 users (show)

See Also:	1484405
Fixed In Version:	rubygem-katello-3.0.0.161-1
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Clones:	1530704 (view as bug list)
Environment:
Last Closed:	2018-02-05 08:54:34 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
hotfix archive (3.70 MB, application/x-gzip) 2018-01-15 17:18 EST, Mike McCune	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Foreman Issue Tracker	18533	None	None	None	2017-02-18 11:58 EST
Red Hat Product Errata	RHSA-2018:0273	normal	SHIPPED_LIVE	Important: Red Hat Satellite 6 security, bug fix, and enhancement update	2018-02-07 19:35:29 EST

Groups: None (edit)

Comment 2 pm-sat@redhat.com 2017-02-18 12:03:23 EST

Upstream bug assigned to tomckay@redhat.com

Comment 4 pm-sat@redhat.com 2017-03-30 12:04:18 EDT

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

Comment 6 jcallaha 2017-11-03 11:33:08 EDT

*** Bug 1484405 has been marked as a duplicate of this bug. ***

Comment 7 Jitendra Yejare 2017-12-06 07:13:46 EST

Verified!

@ Satellite 6.3 snap 27

Steps:

# hammer product create --organization-id 1 --name TestContainerImages --label testcontainerimages --description "Test Container Images"
Product Created

# hammer repository create --organization-id 1 --product TestContainerImages --name Test32Chars --label test32chars --content-type docker --url https://registry.hub.docker.com/ --docker-upstream-name openshift3/ose-metrics-hawkular-openshift-agent
Repository created

Hence moving the state to Verified.

Comment 8 Jitendra Yejare 2018-01-15 05:05:26 EST

Verified!

@ Satellite 6.2.14 snap 1.0

# hammer product create --organization-id 1 --name TestContainerImages --label testcontainerimages --description "Test Container Images"
Product created


# hammer repository create --organization-id 1 --product TestContainerImages --name Test32Chars --label test32chars --content-type docker --url https://registry.hub.docker.com/ --docker-upstream-name openshift3/ose-metrics-hawkular-openshift-agent
Repository created

Comment 9 Mike McCune 2018-01-15 17:18:17 EST

*** HOTFIX INSTRUCTIONS ***

We have made a hotfix available for customers using Satellite 6.2.13. This patch is available for 6.2.13 only and will be released formally in 6.2.14

Instructions:

1) Download attached hotfix-1424689.tar.gz archive containing hotfix and copy to your Satellite server

2) unpack archive: tar xvzf hotfix-1424689.tar.gz

3) katello-service stop

4) rpm -Uvh tfm-rubygem-katello-3.0.0.158-2.HOTFIXRHBZ1424689.el7sat.noarch.rpm 
 (optionally include the katello_ostree rpm installation if the above returns with a dependency error)

5) katello-service start

Resume operations.

Comment 10 Mike McCune 2018-01-15 17:18 EST

Created attachment 1381771 [details]
hotfix archive

Comment 13 errata-xmlrpc 2018-02-05 08:54:34 EST

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, 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-2018:0273

Note You need to log in before you can comment on or make changes to this bug.