Bug 1319908

Summary:	Cannot publish content view with docker repository.
Product:	Red Hat Satellite	Reporter:	Zach Huntington-Meath <zhunting>
Component:	Content Views	Assignee:	Brad Buckingham <bbuckingham>
Status:	CLOSED ERRATA	QA Contact:	Lukas Pramuk <lpramuk>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.0.4	CC:	bbuckingham, cwelton, ehelms, sthirugn
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
URL:	http://projects.theforeman.org/issues/14305
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-27 09:28:12 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Zach Huntington-Meath 2016-03-21 19:14:37 UTC

How to replicate:

1. Create a new docker repository (I used the default url: https://registry-1.docker.io/ and busybox as upstream repository name.)

2. Sync the new repository.

3. Create a new content view and assign it the docker repository.

4. Publish the content view, it should give the error: Validation failed: Repository URL or Upstream Name is empty. Both are required for syncing from the upstream.

Comment 1 Zach Huntington-Meath 2016-03-21 19:14:39 UTC

Created from redmine issue http://projects.theforeman.org/issues/14305

Comment 3 Bryan Kearney 2016-03-21 22:06:18 UTC

Upstream bug component is Content Views

Comment 4 Brad Buckingham 2016-03-21 22:09:50 UTC

Upstream Katello PR: https://github.com/Katello/katello/pull/5908

Comment 5 Lukas Pramuk 2016-03-24 11:57:46 UTC

VERIFIED.

@Sat6.2.0-Beta-Snap5

Used manual reproducer in comment#0:
Successfully published Docker View version 1.0 and promoted to Library

Comment 8 errata-xmlrpc 2016-07-27 09:28:12 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, 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/RHBA-2016:1501