Bug 2051648
| Summary: | [RFE] Better Detail When Job Fails Due To SSH Problem | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Bernie Hoefer <bhoefer> |
| Component: | Remote Execution | Assignee: | Adam Ruzicka <aruzicka> |
| Status: | CLOSED ERRATA | QA Contact: | Peter Ondrejka <pondrejk> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.10.1 | CC: | aruzicka, lstejska |
| Target Milestone: | 6.12.0 | Keywords: | FutureFeature, Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | tfm-rubygem-smart_proxy_remote_execution_ssh-0.6.0 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-11-16 13:33:25 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
Bernie Hoefer
2022-02-07 17:26:33 UTC
This is being worked on. On a side note, as far as remote execution goes, tasks are not meant to be inspected directly by users and may contain raw data just as you're describing. The best way would be to look at the hosts output (job invocation details page > click hostname in the table below). (In reply to Adam Ruzicka from comment #1) === > This is being worked on. === Great to know. === > The best way would be to look at the hosts output (job invocation details page > click hostname in the table below). === Oh my gosh -- thank you for pointing that out. Although I saw the host name displayed as a web link in the table at the bottom of the job invocation page, I just figured that would take me back to the host's All Hosts page since that was where I had clicked the Schedule Remote Job button. Clicking on the host's name in that table *does* show the plain, understandable reason why the job failed. I was expecting that in the Host Detail button or the Host Task selection from that button's drop-down menu. That link really needs changed from just the host name to "job output for host.example.com" or perhaps that table's column header needs changed from "Host" to "Job Result Details From Host". Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/34363 has been resolved. smart_proxy_remote_execution_ssh-0.6.0 containing the fix for this just went out. Verified on Satellite 6.12 sn3, the messages in host job output are now more telling 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 (Important: Satellite 6.12 Release), 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-2022:8506 |