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.

Bug 1651852

Summary: Missing timeout for "Actions::Katello::Host::Package::Update" task
Product: Red Hat Satellite Reporter: Hao Chang Yu <hyu>
Component: Hosts - ContentAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Stephen Wadeley <swadeley>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4CC: bkearney, ehelms, hyu, jalviso, swadeley
Target Milestone: 6.5.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-katello-3.10.0.24-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-01-26 09:15:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Hao Chang Yu 2018-11-21 04:10:28 UTC
Description of problem:
If gofer of the patching client is not connecting to the Satellite, the Actions::Katello::Host::Package::Update task will wait forever.

The expect behaviour is to wait 20 seconds and timeout if gofer then respond just like "Actions::Katello::Host::Package::Install" task

Adding this seems should work.

--- /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.7.0.41/app/lib/actions/pulp/consumer/content_update.rb	2018-11-21 15:08:02.227949116 +1100
+++ /tmp/content_update.rb	2018-11-21 15:07:31.069169127 +1100
@@ -15,10 +15,12 @@
           options = { "importkeys" => true }
           options[:all] = true if input[:args].blank?
 
-          pulp_extensions.consumer.update_content(input[:consumer_uuid],
+          task = pulp_extensions.consumer.update_content(input[:consumer_uuid],
                                                   input[:type],
                                                   parse_units_for_type,
                                                   options)
+          schedule_timeout(Setting['content_action_accept_timeout'])
+          task
         end


Actual results:
Task "Waiting for Pulp" forever


Expected results:
Task failed with:
Host did not respond within 20 seconds. The task has been cancelled. Is katello-agent installed and goferd running on the Host?

Comment 2 Christine Fouant 2019-02-01 14:45:49 UTC
Created redmine issue https://projects.theforeman.org/issues/25965 from this bug

Comment 3 Bryan Kearney 2019-02-01 17:09:39 UTC
Upstream bug assigned to cfouant

Comment 4 Bryan Kearney 2019-02-01 17:09:40 UTC
Upstream bug assigned to cfouant

Comment 5 Bryan Kearney 2019-02-05 15:08:24 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25965 has been resolved.

Comment 13 errata-xmlrpc 2019-05-14 12:39:03 UTC
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-2019:1222