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 2216017 - tasks got stuck while running REX via mqtt mode
Summary: tasks got stuck while running REX via mqtt mode
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Remote Execution
Version: 6.13.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.15.0
Assignee: Adam Ruzicka
QA Contact: Peter Ondrejka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-19 17:54 UTC by Imaan
Modified: 2024-04-23 17:11 UTC (History)
3 users (show)

Fixed In Version: rubygem-smart_proxy_remote_execution_ssh-0.10.2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-04-23 17:11:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 36615 0 Normal Closed MQTT dispatcher gets reset on exceptions instead of just being resumed 2024-01-15 13:26:21 UTC
Red Hat Issue Tracker SAT-20454 0 None None None 2023-09-27 13:27:48 UTC
Red Hat Product Errata RHSA-2024:2010 0 None None None 2024-04-23 17:11:30 UTC

Description Imaan 2023-06-19 17:54:56 UTC
Description of problem:

tasks got stuck while running REX via mqtt. 90% job is executed successfully and rest got stuck and after 2-3 hours, checked the status - which shows the task is in running state (stuck state) but when you click the job data it shows the job has been completed successfully. For example - 3113 out of 3375 completed successfully but 216 got stuck and 46 were shown failed.
							
Version-Release number of selected component (if applicable):

Satellite 6.13.1 snap 1.0

Steps to Reproduce:

Run REX via mqtt mode

Actual results:

some of the tasks got stuck. 

Expected results:

It should show tasks status either success or failed.

Comment 1 Adam Ruzicka 2023-06-19 18:18:59 UTC
What do the smart proxy logs say?

Comment 2 Adam Ruzicka 2023-09-27 13:25:06 UTC
I'll go ahead an assume this was because of https://projects.theforeman.org/issues/36615

Comment 3 Bryan Kearney 2023-10-25 16:02:29 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36615 has been resolved.

Comment 5 Peter Ondrejka 2024-01-17 15:08:21 UTC
Verified on Sat 6.15 sn 6 by stopping and restarting mosquitto. The job is successfully picked up and no longer hangs

Comment 8 errata-xmlrpc 2024-04-23 17:11:29 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 (Important: Satellite 6.15.0 release), 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-2024:2010


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