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.

Created attachment 1347097 [details]
Foreman debug

Description of problem: Traces has helps that the user can run to resolve the issues it finds. Most of those helps are commands like "systemctl restart <service>" but some of them content sentence to tell the user what to do. For example:

```
You will have to reboot your computer
```

This text will get run as a Remote execution command 


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


How reproducible: Always


Steps to Reproduce:
1. On a host with traces error navigate to Content Hosts -> select host -> Traces
2. Run a help that contains anything other than a command. For example "please reboot your computer"


Actual results: A Rex command gets run that is successful, but has an error in the output (see BZ 1508951) 


Expected results: Either the user is instructed to manual perform the task, or the remote execution job reboots the computer. 


Additional info:

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

Sean,

This didn't cherry-pick cleanly, and I'm not that familiar with the codebase.  Could you do the pick for me?

Thanks,
Patrick

Version tested:
Satellite 6.3 snap 30

1. Navigated to Content Hosts -> select host -> Traces
2. Restart selected where helper having "You will have to reboot your computer"

The remote execution job performs reboot but the job failed due to BZ 1531127.
Adding the dependency of BZ 1531127.

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, 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-2018:0336

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