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 1293984 - If client operation (i.e. package install) fails, relevant task in Satellite should fail as well
Summary: If client operation (i.e. package install) fails, relevant task in Satellite ...
Keywords:
Status: CLOSED DUPLICATE of bug 1262940
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.1.5
Hardware: All
OS: Linux
medium
medium
Target Milestone: Unspecified
Assignee: Stephen Benjamin
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-23 21:57 UTC by Pavel Moravec
Modified: 2019-09-12 09:38 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-25 08:50:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Pavel Moravec 2015-12-23 21:57:11 UTC 
Description of problem:
If client operation (i.e. yum install package / apply errata / ..) fails, relevant task in Satellite is marked as success. That confuses Satellite's user wrongly assuming the operation succeeded (i.e. critical security errata applied successfully).

There can be numerous reasons why such operation might fail:
- 403 error
- package already installed (should we report this as failure?)
- yum error like bz1293982 (see reproducer there, will post Satellite's task details of "success" here)
- rpm DB error
- ..

I expect the bug is in pulp task, since the pulp_task output contains proper failure info not propagated further - please reassign elsewhere (goferd? or foreman task?) if I am wrong with the assumption.


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


How reproducible:
should be 100%


Steps to Reproduce:
1. See problem description - many scenarios can exist. If unsure / unable to find one, I can help.


Actual results:
foreman task in Satellite is marked as success, despite pulp task apparently failed (or the yum work did, at least)


Expected results:
foreman task to be marked as failed


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