Bug 1278784

Summary: sosreport can not be killed with SIGTERM
Product: [Fedora] Fedora Reporter: Marius Vollmer <mvollmer>
Component: sosAssignee: Bryn M. Reeves <bmr>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: bmr, jmoran
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 18:25:50 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 Marius Vollmer 2015-11-06 12:09:05 UTC
Killing a sosreport process with SIGTERM does not stop it.  Instead, one gets

    caught exception in plugin method "selinux.collect()"
    writing traceback to sos_logs/selinux-plugin-errors.txt

Steps:

 # sosreport --batch

While that runs in another shell:

 # pkill sosreport

Using "pkill -SIGINT sosreport" works as expected.

Comment 1 Bryn M. Reeves 2015-11-10 15:47:02 UTC
Thanks - filed as upstream issue #689:

  https://github.com/sosreport/sos/issues/689

Comment 2 Fedora End Of Life 2016-07-19 18:25:50 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.