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.
DescriptionAmar Huchchanavar
2016-08-10 15:02:10 UTC
Description of problem:
Since upgrading to Satelite 6.2 from 6.1, when we add a new version of a puppet module, then publish a new content view (and promote it), the puppet repo sync fails to capsule servers (pulp nodes). The error includes "PLP0034" and "pulp.server.controllers.repository:INFO: duplicate unit names".
~~~
Error:
Katello::Errors::PulpError
PLP0034: The distributor RedHat-Library-RHEL7Base indicated a failed response when publishing repository RedHat-Library-RHEL7Base.
~~~
Version-Release number of selected component (if applicable):
Satellite 6.2.0
How reproducible:
Always
Steps to Reproduce:
1.Sync/upload puppet a module with multiple versions.(Eg : motd 1.2.0 and motd 1.2.1)
2.Associate a environment to the capsule.
3.Publish a content view with motd-1.2.0 and promote it to the capsule associated environment.
4.Let the auto-synchronization complete.
5.Now, add motd 1.2.1 module to the same content view and perform the publish-promote task.
6.This time auto-sync will fail with 'PLP0034' error.
Actual results:
Auto-capsule-sync fails with an error 'PLP0034'
Expected results:
It should not fail and complete the action.
Additional info:
Digging further into the problem, customer found that on the capsule servers that the previous version of the puppet module is still included in the puppet repo to be sync'd, in addition to the new version of the puppet module. Since there are 2 versions of the same module in the repo, the sync fails.
hotfix rpm attached as tfm-rubygem-katello-3.0.0.73-1.hotfix.1368746_1365952.el7sat.noarch.rpm (sha1sum 2ced03a29a9c24551dc8dec2ca3a40fd2491b7de)
note: HF package contains fix for this bug and for 1368746 (gofer restart creates applicability regeneration)
to apply:
* rpm -Uvh tfm-rubygem-katello-3.0.0.73-1.hotfix.1368746_1365952.el7sat.noarch.rpm
* katello-service restart
The code change is only needed on the satellite, not capsule
Verified in Satellite 6.2.2 Snap 2
After following the steps outlined in the bug report, no issues encountered during capsule sync. The old version of the module was disassociated with the content view and the new one replaced the old throughout the content view and on the capsule's filesystem.
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:1993