Currently the setup_autorun() method expects the user-defined signal,
SIGUSR1, to generate Guru Meditation Report upon killing a Nova Compute
process, while supplying the said signal.
However, testing in a DevStack environment, manually attempting to kill
a Nova Compute process with SIGUSR1 [kill -s USR1 `pgrep nova-compute`]
does not result in the process being terminated, and no error report is
generated.
It turns out[*] that SIGUSR1 is used by Apache 'mod_wsgi'.
Using, the other user-defined signal, SIGUSR2 resolves this issue (i.e.
'nova-compute' process is terminated, and the Guru Meditation Report is
generated successfully).
So, use the signal USR2 instead of USR1. Also, update the corresponding
tests.
DocImpact: With this patch merged, to generate a successful Guru
Meditation Report, supply the signal USR2 while killing a
Nova Compute process [`kill -s USR2 `pgrep nova-compute`].
[*] https://code.google.com/p/modwsgi/wiki/ConfigurationDirectives#WSGIRestrictSignal
Change-Id: I9d3b6079ba2cca41fe4723723a6f80b2c3c0b9c0
45b1c02d11