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 1337979

Summary: Error in bg while syncing Capsule from satellite containing puppet module
Product: Red Hat Satellite Reporter: Jitendra Yejare <jyejare>
Component: PulpAssignee: John Mitsch <jomitsch>
Status: CLOSED ERRATA QA Contact: Jitendra Yejare <jyejare>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: bbuckingham, bkearney, bmbouter, daviddavis, dkliban, ggainey, hmore, ipanova, jomitsch, mhrivnak, mmccune, pcreech, rchan, sghai, ttereshc
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-21 17:04:42 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:

Comment 1 John Mitsch 2016-05-20 17:15:40 UTC 
Created a new bug about the missing content https://bugzilla.redhat.com/show_bug.cgi?id=1338009
since that is probably unrelated to this error:

pulp: pulp_puppet.plugins.importers.directory:ERROR: Fetch URL: https://qeblade36.rhq.lab.eng.bos.redhat.com/pulp/puppet/Default_Organization-Library-puppet_cv/PULP_MANIFEST failed: Not Found 

This bug's scope should be about the pulp error (PULP_MANIFEST failed: Not Found)
Comment 4 John Mitsch 2016-06-07 14:46:07 UTC 
Bryan,

There was a bit of confusion about this bug. It is really two issues

1) Puppet module content is not showing up on the capsule, which has been filed https://bugzilla.redhat.com/show_bug.cgi?id=1338009 and is in POST

2) an error in the background that doesn't seem to be affecting anything (as far as I can tell) but still should be fixed. The error is " pulp_puppet.plugins.importers.directory:ERROR: Fetch URL: https://qeblade36.rhq.lab.eng.bos.redhat.com/pulp/puppet/Default_Organization-Library-puppet_cv/PULP_MANIFEST failed"

These appear to be unrelated.

I can look into the error and talk to the pulp team about it.
Comment 5 John Mitsch 2016-06-07 15:25:05 UTC 
Linking this to a pulp issue, it appears that this error isn't affecting anything in Satellite, but rather is pulp checking for a PULP_MANIFEST in puppet forge repos and then syncing to puppet forge when it doesn't find anything. This is logged when it probably shouldn't be.
Comment 7 John Mitsch 2016-07-22 19:12:53 UTC 
*** Bug 1323961 has been marked as a duplicate of this bug. ***
Comment 8 pulp-infra@redhat.com 2016-11-21 18:53:52 UTC 
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
Comment 9 pulp-infra@redhat.com 2016-11-21 18:53:56 UTC 
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 10 pulp-infra@redhat.com 2016-12-13 11:32:38 UTC 
The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug.
Comment 11 pulp-infra@redhat.com 2016-12-14 16:01:55 UTC 
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
Comment 12 pulp-infra@redhat.com 2016-12-14 17:01:55 UTC 
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
Comment 13 pulp-infra@redhat.com 2016-12-14 17:31:44 UTC 
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
Comment 14 pulp-infra@redhat.com 2017-01-10 02:03:00 UTC 
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
Comment 15 pulp-infra@redhat.com 2017-01-16 21:03:17 UTC 
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Comment 16 Jitendra Yejare 2017-10-17 13:37:35 UTC 
Verified !

@ Satellite 6.3 snap 20

Steps:

1) created a product
2) created a puppet repo
3) added puppet modules to that repo
4) created a content view
5) add puppet modules to that content view
6) published and promoted that content view as capsule was associated with DEV env
7) Sync capsule automatically triggered


Observed:

1. No Error in /var/log/messages as mentioned in Description.
2. Puppet module is synced to capsule and can be found in correct directory
Comment 17 Bryan Kearney 2018-02-21 17:04:42 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/RHSA-2018:0336