Description of problem: When client is executing remote script with some output and rhn_check process gets killed (e.g. BZ#1494389 and BZ#1260527) we can store the partial output and then resend it back to Satellite in case the action is picked up again in pending state (for 2nd time) Version-Release number of selected component (if applicable): rhncfg-5.10.87-11 How reproducible: always Steps to Reproduce: 1. schedule remote command like: #!/bin/sh echo bla bla sleep 10 2. rhn_check -vv on the client 3. once it's visible from rhn_check's output that the actions has started it's execution run: pkill -KILL rhn_check Actual results: no previous output is sent back to satellite Expected results: At least some output is either stored on the client or send back to satellite. Additional info: Typical use case are remote commands like "yum update && reboot" and osad running on client.
spacewak.git(master): 67f94213d29facb3925f6063bd41bf8ca33b0c95 Won't work without updated rhn_check, but cuases no harm without it.
spacewalk.git(master): bb58e1a4ef55f1130ee1f591b89d58388ecb8969
Verified with: rhncfg-5.10.87-12.el7sat.noarch rhnlib-2.5.65-7.el7.noarch Reproducer same as Description SIGTERM: Client execution returned "Termination signal occurred during execution." (code 255) SIGKILL: Client execution returned "Previous run of action didn't completed sucessfully, aborting." (code 255)
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/RHBA-2018:0137