Bug 1338009

Summary:	Puppet repo content missing on capsule
Product:	Red Hat Satellite	Reporter:	John Mitsch <jomitsch>
Component:	Foreman Proxy	Assignee:	John Mitsch <jomitsch>
Status:	CLOSED ERRATA	QA Contact:	Jitendra Yejare <jyejare>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.2.0	CC:	bbuckingham, bkearney, bmbouter, cwelton, daviddavis, dkliban, ehelms, ggainey, ipanova, jhutar, jyejare, mhrivnak, pcreech, rchan, ttereshc
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	pulp-puppet-2.8.3.2-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-27 10:59:05 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:

Description John Mitsch 2016-05-20 17:13:44 UTC

Description of problem:

When syncing puppet repositories to a capsule through a content view there is no content available in the folder path on the capsule for that puppet repository. When syncing a puppet module that is part of a repository in Library to a capsule, the puppet module is in the correct location on the capsule.

For example:

On the capsule, I see the puppet module for the Library repository
/var/lib/pulp/published/puppet/https/repos/Default_Organization-puppet_pro-puppet_repo/system/releases/o/openstack/openstack-nova-7.0.0.tar.gz

but (still on the capsule) when I check for the puppet module for the content view, it is not there.

/var/lib/pulp/published/puppet/https/repos/Default_Organization-Library-puppet_cv/


Version-Release number of selected component (if applicable):


How reproducible:
%100

Steps to Reproduce:
1.Upload a puppet module to a repository
2.Create a content view in Library with that puppet module
3.Sync a capsule with Library environment
4.Check for puppet module content in /var/lib/pulp/published/puppet/https/repos/<content view directory>/

Actual results:

No puppet module exists in the correct file location on a capsule

Expected results:

The content exists in the correct location

Additional info:

Comment 1 John Mitsch 2016-05-23 15:52:59 UTC

This is blocking syncing puppet repos properly to a capsule

Comment 3 John Mitsch 2016-05-24 18:24:07 UTC

PR in pulp is open here:

https://github.com/pulp/pulp_puppet/pull/234

Comment 4 pulp-infra@redhat.com 2016-05-24 18:30:20 UTC

The Pulp upstream bug status is at POST. Updating the external tracker on this bug.

Comment 5 pulp-infra@redhat.com 2016-05-24 18:30:23 UTC

The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.

Comment 6 Mike McCune 2016-05-25 17:46:33 UTC

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

Comment 7 pulp-infra@redhat.com 2016-06-06 20:00:25 UTC

The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.

Comment 9 pulp-infra@redhat.com 2016-06-17 17:30:35 UTC

The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.

Comment 10 pulp-infra@redhat.com 2016-06-27 17:00:42 UTC

The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.

Comment 11 Jitendra Yejare 2016-07-01 11:09:37 UTC

Verified ! 

@ Sat 6.2 Snap 18.1 GA

On syncing capsule, the puppet module is copied to published/promoted CV folder in capsule.

# ll /var/lib/pulp/published/puppet/https/repos/Default_Organization-Dev-puppet_cv/system/releases/j/jfryman/jfryman-selinux-0.3.1.tar.gz 

-> lrwxrwxrwx. 1 apache apache 136 Jul  1 06:57 /var/lib/pulp/published/puppet/https/repos/Default_Organization-Dev-puppet_cv/system/releases/j/jfryman/jfryman-selinux-0.3.1.tar.gz -> /var/lib/pulp/content/units/puppet_module/46/1f06507db135e9342f5a2a77721fa22a94c39d855e639efc1740cafc1053f5/jfryman-selinux-0.3.1.tar.gz


So moving this bz to Verified !

Comment 12 Bryan Kearney 2016-07-27 10:59:05 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