Bug #11810
closed
Install erratum fails because gofer/katello-agent doesn't send the response back?
Description
When updating packages from katello, gofer installs the new version, but katello task fails with:
2015-09-15 05:42:18 [foreman-tasks/action] [E] Host did not respond within 40 seconds. Is katello-agent installed and goferd running on the Host? (RuntimeError)
| /opt/rh/ruby193/root/usr/share/gems/gems/katello-2.3.0/app/lib/actions/pulp/consumer/abstract_content_action.rb:22:in `process_timeout'
| /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.8.5/lib/dynflow/action/polling.rb:23:in `run'
...
Those are the messages from the client:
2015-09-15T05:41:39.243590-04:00 alto.domain.net goferd: [INFO][worker-0] gofer.messaging.adapter.proton.connection:100 - connecting: URL: amqps://puppet.domain.net:5647|SSL: ca: /var/lib/puppet/ssl/certs/ca.pem|key: None|certificate: /etc/pki/puppet_certs/katello_agent/katello_agent_certs.pem|host-validation: None
2015-09-15T05:41:39.275611-04:00 alto.domain.net ▒<30>goferd: [INFO][worker-0] root:481 - connecting to puppet.domain.net:5647...
2015-09-15T05:41:39.331334-04:00 alto.domain.net goferd: [INFO][worker-0] gofer.messaging.adapter.proton.connection:103 - connected: amqps://puppet.domain.net:5647
2015-09-15T05:41:39.331940-04:00 alto.domain.net ▒<30>goferd: [INFO][worker-0] root:501 - connected to puppet.domain.net:5647
2015-09-15T05:41:40.201130-04:00 alto.domain.net goferd: [INFO][worker-0] gofer.rmi.dispatcher:600 - call: Content.install() sn=ffcb000d-adf9-4a10-b554-467563fc5aa3 data={'task_id': '8038cb1e-cd0e-46d9-92fe-5c830aff96be', 'consumer_id': 'a7e142c8-ed04-4bf3-9043-2b31afb46899'}
Updated by Eric Helms almost 9 years ago
- Category set to Client/Agent
- Translation missing: en.field_release set to 70
- Triaged changed from No to Yes
Updated by Justin Sherrill almost 9 years ago
- Status changed from New to Need more information
- Assignee set to Justin Sherrill
- Translation missing: en.field_release changed from 70 to 86
This seems to indicate some issue, likely on the agent side. This works on a normal install. Is this still a problem?
Updated by Eric Helms over 8 years ago
- Status changed from Need more information to Resolved
Please let us know if you still see this issue with Katello 3.0