Description of problem: Currently in order to upgrade an existing Satellite 6.0.8 instance to latest Satellite 6.1.0 snap requires us to manually stop a few pulp services before you can perform the upgrade: * for app in pulp_workers pulp_celerybeat pulp_resource_manager; do service $app stop; done ... and then run the upgrade, which I believe may restart qpidd * katello-installer --upgrade Even if this step won't restart qpidd, if you were to restart it, then you start seeing the maximum recursion depth exceeded (see attached stacktrace) Version-Release number of selected component (if applicable): libqpid-dispatch-0.4-2.20150223.el6.x86_64 mod_wsgi-3.4-1.pulp.el6sat.x86_64 omaciel-rhel-6-satellite-60.cfme.lab.eng.rdu2.redhat.com-qpid-broker-1.0-1.noarch omaciel-rhel-6-satellite-60.cfme.lab.eng.rdu2.redhat.com-qpid-client-cert-1.0-1.noarch omaciel-rhel-6-satellite-60.cfme.lab.eng.rdu2.redhat.com-qpid-router-client-1.0-1.noarch omaciel-rhel-6-satellite-60.cfme.lab.eng.rdu2.redhat.com-qpid-router-server-1.0-1.noarch pulp-docker-plugins-0.2.2-1.el6_6sat.noarch pulp-katello-0.3-4.el6sat.noarch pulp-nodes-common-2.6.0-0.7.beta.1.el6_6sat.noarch pulp-nodes-parent-2.6.0-0.7.beta.1.el6_6sat.noarch pulp-puppet-plugins-2.6.0-0.7.beta.el6sat.noarch pulp-puppet-tools-2.6.0-0.7.beta.el6sat.noarch pulp-rpm-plugins-2.6.0-0.7.beta.el6_6sat.noarch pulp-selinux-2.6.0-0.7.beta.1.el6_6sat.noarch pulp-server-2.6.0-0.7.beta.1.el6_6sat.noarch python-gofer-qpid-2.6.0-1.el6_6sat.noarch python-isodate-0.5.0-4.pulp.el6_6sat.noarch python-kombu-3.0.24-5.pulp.el6_6sat.noarch python-kombu-3.0.24-5.pulp.el6_6sat.noarch python-pulp-bindings-2.6.0-0.7.beta.1.el6_6sat.noarch python-pulp-common-2.6.0-0.7.beta.1.el6_6sat.noarch python-pulp-docker-common-0.2.2-1.el6_6sat.noarch python-pulp-puppet-common-2.6.0-0.7.beta.el6sat.noarch python-pulp-rpm-common-2.6.0-0.7.beta.el6_6sat.noarch python-qpid-0.30-5.el6.noarch python-qpid-qmf-0.30-4.el6.x86_64 qpid-cpp-client-0.30-6.el6.x86_64 qpid-cpp-client-devel-0.30-6.el6.x86_64 qpid-cpp-server-0.30-6.el6.x86_64 qpid-cpp-server-linearstore-0.30-6.el6.x86_64 qpid-dispatch-router-0.4-2.20150223.el6.x86_64 qpid-java-client-0.30-3.el6.noarch qpid-java-common-0.30-3.el6.noarch qpid-proton-c-0.9-1.20150223.el6.x86_64 qpid-qmf-0.30-4.el6.x86_64 qpid-tools-0.30-3.el6.noarch ruby193-rubygem-qpid_messaging-0.30.0-1.el6_6sat.x86_64 rubygem-smart_proxy_pulp-1.0.1.1-1.el6_6sat.noarch How reproducible: Steps to Reproduce: 1. Install Satellite-6.1.0-RHEL-6-20150310.0 compose 2. Stop pulp services 3. Re-start qpidd Actual results: See attached log Expected results: Additional info:
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.
This appears to be another incident of BZ1178829. The fix is described in https://bugzilla.redhat.com/show_bug.cgi?id=1178829#c10
I upgrade sat6.0.8 to sat6.1 GA snap3 compose2. Upgrade was successful and I restarted qpidd along with some pulp-services.. I didn't see any issue except this: https://bugzilla.redhat.com/show_bug.cgi?id=1220771
Thanks to the help of Brian Bouterse I was able to verify this BZ. The steps are included on comment #11.
This bug is slated to be released with Satellite 6.1.
This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days