Bug 2066870 - Satellite task result is showing state pending and result success state
Summary: Satellite task result is showing state pending and result success state
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Dynflow
Version: 6.10.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
: 2066869 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-22 16:29 UTC by Sneha Arya
Modified: 2023-08-14 09:10 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-14 09:10:06 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Sneha Arya 2022-03-22 16:29:59 UTC
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:
~~~

Comment 2 Brad Buckingham 2022-03-24 14:22:27 UTC
Would it be possible to attach the stack trace for when the error occurs?

Comment 5 Adam Ruzicka 2022-04-26 12:04:57 UTC
*** Bug 2066869 has been marked as a duplicate of this bug. ***

Comment 7 Adam Ruzicka 2023-08-14 09:10:06 UTC
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.


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