Bug 1543636
Summary: | Remote Execution SSH-based Power Action remains pending despite having successfully rebooted the host | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Pablo Hess <phess> |
Component: | Remote Execution | Assignee: | satellite6-bugs <satellite6-bugs> |
Status: | CLOSED ERRATA | QA Contact: | Jameer Pathan <jpathan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.2.14 | CC: | aruzicka, bbuckingham, brcoca, briasmit, bruce.howells, fgarciad, inecas, jalviso, jjansky, jpathan, m.r.watts, pmoravec, rlavande, suarora, wpinheir |
Target Milestone: | 6.4.0 | Keywords: | Triaged |
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: | 2018-10-16 18:53:28 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
Pablo Hess
2018-02-08 21:24:12 UTC
I see the same thing when trying to restart RHEL 7 clients; the reboot works but the job never succeeds. As a workaround, I've cloned the "Power Action - SSH Default" template and modified it to do this: echo <%= input('action') %> host && sleep 3 <%= case input('action') when 'restart' 'shutdown -r +1' else 'shutdown -h now' end %> This seems to work fine, albeit with a 1 minute delay. Technical cause for the never-completed task is simply the fact that the "reboot" command might not return success return value, before network goes down during the already-initiated shutdown/reboot. Therefore "reboot -r +1" or other modification _ensuring_ the latest command will _always_ return success is a valid workaround/solution. I created foreman issue for it and will open PR - let see what upstream community feedback will be. IMHO every solution has its own limitation.. Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/22679 has been resolved. Verified: @satellite 6.4.0 snap 16 Steps: 1. On the webUI, run a remote execution job. 2. Select "Power Action - SSH Default" as Job Template, then insert target host(s) and set "restart" for action. 3. Execute it immediately. Observation -the host reboots successfully, the task enter stopped-success state. 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:2927 |