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: