Bug 1769821

Summary: Remote execution failed as exit code of yum check-update is 100
Product: Red Hat Satellite Reporter: Surjeet Salvi <susalvi>
Component: Remote ExecutionAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Peter Ondrejka <pondrejk>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.4CC: aruzicka, inecas
Target Milestone: Unspecified   
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: 2019-11-07 14:58:34 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:

Description Surjeet Salvi 2019-11-07 14:51:12 UTC
1. Proposed title of this feature request
Do not show return code 100 as FAILED in Remote Execution Jobs

2. Who is the customer behind the request?
Taylor Corporation
     Account: name (acct #) - 370238

     TAM customer: no


     SRM customer: no


     Strategic: no


3. What is the nature and description of the request?
I patch my content hosts via REX.  When I issue yum commands, often a return code of 100 is raised.  This >0 return code
causes REX to report fail.  It is unacceptable that I investigate every REX fail for return code 100.

4. Why does the customer need this? (List the business requirements here)
It is unacceptable that I investigate every REX fail for return code 100.

5. How would the customer like to achieve this? (List the functional requirements here)
Do not have REX report failure for return code 100.

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
Success is when REX does not report a failure for return code 100.

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
I don't know.

8. Does the customer have any specific time-line dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
No.

9. Is the sales team involved in this request and do they have any additional input?
No

10. List any affected packages or components.
Satellite.

11. Would the customer be able to assist in testing this functionality if implemented?

Comment 3 Adam Ruzicka 2019-11-07 14:58:34 UTC
This is most likely a duplicate of BZ1685738, if you think this BZ describes something different, feel free to reopen it.

*** This bug has been marked as a duplicate of bug 1685738 ***