Bug 1860014

Summary:	Foreman tasks return final "success" result, but stay in "running" state
Product:	Red Hat Satellite	Reporter:	Dylan Gross <dgross>
Component:	Tasks Plugin	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Peter Ondrejka <pondrejk>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.7.0	CC:	aruzicka, pdwyer, pmoravec
Target Milestone:	Unspecified	Keywords:	MigratedToJIRA, Triaged
Target Release:	Unused
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-05 21:38:20 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 Dylan Gross 2020-07-23 14:21:14 UTC

Description of problem:

  A number of Actions::Katello::Host::UploadPackageProfile tasks every night will end up with a "success" result, but will forever remain in "Running" state.

Version-Release number of selected component (if applicable):

   Satellite 6.7.1

How reproducible:   Unknown (likely load related)
Steps to Reproduce:

Actual results:

   The number of tasks will vary every night, as will the host IDs related to the UploadPackageProfile task.   The constant is that these usually happen during the night when nightly repo syncs and Content View promotions are happening.

Expected results:

  When a task returns a success result, it should also leave the running state.

Additional info:

  This is adding daily task cleanup work to the admins every day as they make sure these tasks aren't problematic

Comment 10 Brad Buckingham 2023-02-01 19:24:14 UTC

Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 14 Eric Helms 2024-06-05 21:38:20 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.