Red Hat Bugzilla – Bug 1198797
Remote Install fails due to pulp error
Last modified: 2017-02-23 15:23:26 EST
Created attachment 998044 [details] Content host pulp error log Description of problem: Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Create multiple content views, publish, promote 2. Register/subscribe multiple content hosts to different content view 3. Attempt to apply an applicable errata on different content hosts pertaining to different content views Actual results: Content view is updated but failed in applying the errata to the content hosts. Content host /var/log/messages is attached Expected results: Incremental update is completed Additional info:
Version Tested: *************** Satellite-6.1.0-RHEL-6-20150303.0 In rhel 6.6 satellite 6.1: ************************** # rpm -qa | grep pulp pulp-puppet-tools-2.6.0-0.7.beta.el6sat.noarch python-kombu-3.0.24-5.pulp.el6_6sat.noarch pulp-katello-0.3-4.el6sat.noarch pulp-rpm-plugins-2.6.0-0.7.beta.el6_6sat.noarch python-pulp-common-2.6.0-0.7.beta.el6_6sat.noarch python-pulp-docker-common-0.2.2-1.el6_6sat.noarch python-pulp-bindings-2.6.0-0.7.beta.el6_6sat.noarch pulp-server-2.6.0-0.7.beta.el6_6sat.noarch pulp-nodes-parent-2.6.0-0.7.beta.el6_6sat.noarch rubygem-smart_proxy_pulp-1.0.1.1-1.el6_6sat.noarch python-pulp-rpm-common-2.6.0-0.7.beta.el6_6sat.noarch pulp-nodes-common-2.6.0-0.7.beta.el6_6sat.noarch pulp-selinux-2.6.0-0.7.beta.el6_6sat.noarch pulp-docker-plugins-0.2.2-1.el6_6sat.noarch python-isodate-0.5.0-4.pulp.el6_6sat.noarch python-pulp-puppet-common-2.6.0-0.7.beta.el6sat.noarch mod_wsgi-3.4-1.pulp.el6sat.x86_64 pulp-puppet-plugins-2.6.0-0.7.beta.el6sat.noarch In rhel 6.6 content host: ************************ # rpm -qa | grep pulp python-isodate-0.5.0-4.pulp.el6_6sat.noarch pulp-rpm-handlers-2.6.0-0.7.beta.el6_6sat.noarch python-pulp-common-2.6.0-0.7.beta.el6_6sat.noarch python-pulp-rpm-common-2.6.0-0.7.beta.el6_6sat.noarch python-pulp-agent-lib-2.6.0-0.7.beta.el6_6sat.noarch
Looks like an issue in the reconnect logic in the gofer proton adapter. Fixing in gofer upstream.
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.
Fixed in gofer 2.6.0.
Verified. Satellite-6.1.0-RHEL-6-20150317.0
This bug is slated to be released with Satellite 6.1.
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-2015:1592