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)
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.
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.
*** Bug 1323961 has been marked as a duplicate of this bug. ***
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug.
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
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
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