Feature #15872
Updated by Ivan Necas almost 8 years ago
It would be nice Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1360293 1. Proposed title of this feature request Ability to be able to make the job execution survive monitor whether a restart (or a temporary Unmanaged host disconnection in general) and continue with the script once it gets back. For now, we were thinking about is up after a special macro in job invocation that reboot through remote execution feature. 2. Who is the smart proxy would understand customer behind the request? Account: name (acct #) 1099189 TAM customer: no/yes no SRM customer: no/yes no Strategic: no/yes yes 3. What is the nature and would split description of the script into request? The remote execution feature only provides the subparts to execute separately, with ability to wait for exit code of the host to be ready between the executions, such as: <pre> yum updtae -y reboot ### WAIT_FOR_RECONNECT ### echo 'Restarted after reboot' >> /etc/motd </pre> This way command executed. So, whether the execution would server was actually up or not, cannot be split into two parts, and monitored. 4. Why does the second part customer need this? (List the business requirements here) Not Available 5. How would be executed after the reboot happens. If customer like to achieve this? (List the second part functional requirements here) Customer is looking for a functionality where they can confirm whether the system was missing (the `### WAIT_FOR_RECONNECT ###` would be successfully up after a reboot through the last line Satellite. 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. NA 7. Is there already an existing RFE upstream or in Red Hat Bugzilla? No 8. Does the template, it customer have any specific timeline dependencies and which release would serve just as waiting for they like to target (i.e. RHEL5, RHEL6)? No 9. Is the reconnection, as required by sales team involved in this RFE. The `### WAIT_FOR_RECONNECT ###` macro could request and do they have any additional input? No 10. List any affected packages or components. NA 11. Would the customer be used multiple times able to assist in the job. testing this functionality if implemented? Yes