Bug 1457938 - goferd failed to connect to satellite amqps service
Summary: goferd failed to connect to satellite amqps service
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Qpid
Version: 6.2.10
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: Unspecified
Assignee: Mike Cressman
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks: 1457977
TreeView+ depends on / blocked
 
Reported: 2017-06-01 15:15 UTC by Djebran Lezzoum
Modified: 2017-09-14 17:06 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1457977 (view as bug list)
Environment:
Last Closed: 2017-09-14 17:06:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Djebran Lezzoum 2017-06-01 15:15:21 UTC
Created attachment 1284171 [details]
foreman-debug output

Description of problem:
when trying to do hammer host-collection erratum install, installation sub task error returned

Version-Release number of selected component (if applicable):
* candlepin-0.9.54.21-1.el7.noarch
* candlepin-selinux-0.9.54.21-1.el7.noarch
* foreman-1.11.0.76-1.el7sat.noarch
* foreman-compute-1.11.0.76-1.el7sat.noarch
* foreman-debug-1.11.0.76-1.el7sat.noarch
* foreman-discovery-image-3.1.1-23.el7sat.noarch
* foreman-ec2-1.11.0.76-1.el7sat.noarch
* foreman-gce-1.11.0.76-1.el7sat.noarch
* foreman-installer-1.11.0.15-2.el7sat.noarch
* foreman-installer-katello-3.0.0.84-1.el7sat.noarch
* foreman-libvirt-1.11.0.76-1.el7sat.noarch
* foreman-openstack-1.11.0.76-1.el7sat.noarch
* foreman-ovirt-1.11.0.76-1.el7sat.noarch
* foreman-postgresql-1.11.0.76-1.el7sat.noarch
* foreman-proxy-1.11.0.7-1.el7sat.noarch
* foreman-rackspace-1.11.0.76-1.el7sat.noarch
* foreman-selinux-1.11.0.4-1.el7sat.noarch
* foreman-vmware-1.11.0.76-1.el7sat.noarch
* katello-3.0.0-20.el7sat.noarch
* katello-certs-tools-2.4.0-1.el7sat.noarch
* katello-client-bootstrap-1.3.0-1.el7sat.noarch
* katello-common-3.0.0-20.el7sat.noarch
* katello-debug-3.0.0-20.el7sat.noarch
* katello-default-ca-1.0-1.noarch
* katello-installer-base-3.0.0.84-1.el7sat.noarch
* katello-selinux-3.0.1.2-1.el7sat.noarch
* katello-server-ca-1.0-1.noarch
* katello-service-3.0.0-20.el7sat.noarch
* openldap-2.4.40-13.el7.x86_64
* pulp-client-1.0-1.noarch
* pulp-docker-plugins-2.0.3.1-1.el7sat.noarch
* pulp-katello-1.0.2-1.el7sat.noarch
* pulp-ostree-plugins-1.1.3.3-1.el7sat.noarch
* pulp-puppet-plugins-2.8.7.1-1.el7sat.noarch
* pulp-puppet-tools-2.8.7.1-1.el7sat.noarch
* pulp-rpm-plugins-2.8.7.13-1.el7sat.noarch
* pulp-selinux-2.8.7.11-1.el7sat.noarch
* pulp-server-2.8.7.11-1.el7sat.noarch
* python-ldap-2.4.15-2.el7.x86_64
* tfm-rubygem-ldap_fluff-0.4.5-1.el7sat.noarch
* tfm-rubygem-net-ldap-0.13.0-1.el7sat.noarch


How reproducible:
Always

Steps to Reproduce:
1. Setup 2 hosts and a host-collection subscribed to some products containing erratum
2. run:
   hammer host-collection erratum install --id="col-id" --organization-id="org-id" --errata="errata-id"
<<< Message,Id
Successfully scheduled installation of errata,263eea3b-3ac1-4576-9b66-85ce46ec93e9

3. to wait the task to finish run:
    hammer -v -u admin -p changeme  task progress --id="263eea3b-3ac1-4576-9b66-85ce46ec93e9"
     

Actual results:
2 task(s), 0 success, 2 fail

Expected results:
2 task(s), 2 success, 0 fail
and errata successfully installed

Additional info:
1- in the UI Minitor > tasks 
    the tasks error is:
     Host did not respond within 20 seconds. The task has been cancelled. Is katello-agent installed and goferd running on the Host?

2- at one of the virtual machine  /var/log/messages contain error
   Jun  1 10:44:19 139890008902672 goferd: [ERROR][worker-0] gofer.messaging.adapter.connect:33 - connect: proton+amqps://dell-pe-fm120-2a.rhts.eng.bos.redhat.com:5647, failed: Connection amqps://dell-pe-fm120-2a.rhts.eng.bos.redhat.com:5647 disconnected
Jun  1 10:44:19 139890008902672 goferd: [INFO][worker-0] gofer.messaging.adapter.connect:35 - retry in 51 seconds

Comment 6 Bryan Kearney 2017-09-14 17:06:13 UTC
This will be fixed in 6.3 by https://bugzilla.redhat.com/show_bug.cgi?id=1457977. I do not see us backporting this to 6.2.z so I am closing out this bug.


Note You need to log in before you can comment on or make changes to this bug.