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.
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?
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 ***
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?