Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 958740

Summary: Add logging to signal handlers
Product: Red Hat Enterprise Virtualization Manager Reporter: Lee Yarwood <lyarwood>
Component: vdsmAssignee: Assaf Muller <amuller>
Status: CLOSED UPSTREAM QA Contact: Barak Dagan <bdagan>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.1.3CC: amuller, bazulay, danken, hateya, iheim, jkt, lpeer, pstehlik
Target Milestone: ---   
Target Release: 3.3.0   
Hardware: All   
OS: All   
Whiteboard: infra
Fixed In Version: vdsm-4.10.3-0.416.git5358ed2.el6.x86_64 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-18 13:02:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 894399, 902971, 1019461    

Description Lee Yarwood 2013-05-02 10:26:54 UTC 
Description of problem:

There is currently no logging when handling SIGTERM and SIGUSR1 signals sent to vdsm.

vdsm/vdsm

 42     def sigtermHandler(signum, frame):
 43         if cif:
 44             cif.prepareForShutdown()
 45 
 46     def sigusr1Handler(signum, frame):
 47         if cif and cif.irs:
 48             cif.irs.spmStop(
 49                     cif.irs.getConnectedStoragePoolsList()['poollist'][0])

As sanlock can send SIGTERMs to vdsm any logging here would help.

Version-Release number of selected component (if applicable):
4.10.2-1.13

How reproducible:
Always

Steps to Reproduce:
1. Send a SIGTERM or SIGUSR1 to vdsm.
  
Actual results:
Nothing is logged regarding which signal was caught.

Expected results:
The caught signal type is logged in vdsm.log

Additional info: