RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.

Description of problem:
We should be able to deliver exit code of remotely executed commands when restart comes during remote command execution.

Version-Release number of selected component (if applicable):
rhn-client-tools-2.0.2-6.el7

How reproducible:
100%
https://bugzilla.redhat.com/show_bug.cgi?id=1260527

Steps to Reproduce:
1. setup osad on client
2. execute remote command with remoot/shutdown -r now/init 6

Actual results:
reboot loop because of not delivering exit code of remote command

Expected results:
exit code of remote command should be delivered to Satellite, client reboot should follow AFTER that

Additional info:
we need to mask SIGTERM during remote command execution, leftover processes are killed by SIGKILL after 90 seconds, but we should be able to do it faster

We can't fix this due to current systemd behavior. Something needs to be done with BZ#1352264 first...