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.
Description of problem:
Satellite task result is showing state pending and result success state.
Version-Release number of selected component (if applicable):
6.10
How reproducible:
It's rare to reproduce but it occurred in customer's environment.
Additional info:
Foreman rake is failing with following errors:
~~~
# foreman-rake foreman_tasks:export_tasks TASK_SEARCH="id= XYZ
Exporting all tasks matching filter id=XZY
Gathering 1 tasks.
rake aborted!
NoMethodError: undefined method `id' for nil:NilClass
# hammer task info --id XYZ
ID: XYZ
Action:
State: pending
Result: success
Started at:
Ended at:
Owner:
~~~
I'm afraid we don't have enough information to go by here so I'll go ahead and close this. If anyone comes up with a reliable way of reproducing this, please do reopen this bug and we'll take another look at it.