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 2008809

Summary:	Task is failing but still showing success state
Product:	Red Hat Satellite	Reporter:	Kenny Tordeurs <ktordeur>
Component:	Subscription Management	Assignee:	Adam Ruzicka <aruzicka>
Status:	CLOSED ERRATA	QA Contact:	Cole Higgins <chiggins>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.9.0	CC:	ahumbe, aperotti, aruzicka, momran, pcreech, pgiustin, yoliynyk
Target Milestone:	6.11.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-07-05 14:30:00 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:
Bug Depends On:
Bug Blocks:	1399395

Description Kenny Tordeurs 2021-09-29 08:54:13 UTC

Description of problem:
The task has a failed state but shows success without errors.

3: Actions::Candlepin::AsyncHypervisors (success) [ 0.03s / 0.03s ]
---
hypervisors: []
task:
  created: '2021-09-28T20:22:51+0000'
  updated: '2021-09-28T20:22:51+0000'
  id: 8ac983b57bbb12fd017c2e13076c1b29
  name: Hypervisor Update
  group: 
  origin: satellite6-example.local
  executor: 
  principal: foreman_admin
  state: FAILED    <--------
  previousState: CREATED
  startTime: 
  endTime: 
  attempts: 0
  maxAttempts: 1
  statusPath: "/jobs/8ac983b57bbb12fd017c2e13076c1b29"
  key: HypervisorUpdateJob
---

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

How reproducible:
Not easily

Steps to Reproduce:
1.
2.
3.

Actual results:
the state is failed inside the dynflow tasks but the general task is showing success and green state.

Expected results:
Failed red state.

Additional info:

Comment 4 Kenny Tordeurs 2021-09-29 10:46:54 UTC

The problem was resolved by restarting the satellite services. 

while running hammer ping we noticed some failures but checking the logs in /var/log/candlepin/error_log we did not see any evidence of the problem in question but as a test we performed a total restart of the services and then running virt-who --one-shot the task "hypervisorupdate" was successful.

Hammer ping before restart:
[root@satellite ~]# hammer ping
database:         
    Status:          ok
    Server Response: Duration: 0ms
candlepin:        
    Status:          ok
    Server Response: Duration: 19ms
candlepin_events: 
    Status:          ok
    message:         68409 Processed, 12 Failed
    Server Response: Duration: 0ms
candlepin_auth:   
    Status:          ok
    Server Response: Duration: 19ms
katello_events:   
    Status:          ok
    message:         23880 Processed, 1 Failed
    Server Response: Duration: 0ms
pulp:             
    Status:          ok
    Server Response: Duration: 111ms
pulp_auth:        
    Status:          ok
    Server Response: Duration: 70ms
foreman_tasks:    
    Status:          ok
    Server Response: Duration: 4ms

We're grabbing more logs to try and pinpoint these failures.

Comment 6 Adam Ruzicka 2021-09-30 06:39:12 UTC

Created redmine issue https://projects.theforeman.org/issues/33598 from this bug

Comment 7 Bryan Kearney 2021-11-04 13:51:34 UTC

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/33598 has been resolved.

Comment 13 errata-xmlrpc 2022-07-05 14:30:00 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 (Moderate: Satellite 6.11 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-2022:5498

Comment 14 momran 2022-10-12 14:54:48 UTC

*** Bug 2063223 has been marked as a duplicate of this bug. ***