> That sounds like a pretty serious change in behavior to push 2 days before
> carving a release candidate. Could you explain to me why this needs to be
> pushed in Bexar ? I see that the regression risk is contained, however it
> changes the behavior of the software a bit too deeply, a bit too late.
Thierry,
I already discussed that with Soren on IRC last Friday.
With current code we are loosing Python TRACEs (and all other data which Nova sents to STDOUT and STDERR) when Nova daemons properly daemonized.
See bug for details: https://bugs.launchpad.net/nova/+bug/708740
Nova daemon's startup scripts in Ubuntu needs to be slightly modified to run with our code:
s, > /var/log/nova/nova-compute.log,--logfile /var/log/nova/nova-compute.log,
> That sounds like a pretty serious change in behavior to push 2 days before
> carving a release candidate. Could you explain to me why this needs to be
> pushed in Bexar ? I see that the regression risk is contained, however it
> changes the behavior of the software a bit too deeply, a bit too late.
Thierry,
I already discussed that with Soren on IRC last Friday. /bugs.launchpad .net/nova/ +bug/708740
With current code we are loosing Python TRACEs (and all other data which Nova sents to STDOUT and STDERR) when Nova daemons properly daemonized.
See bug for details: https:/
Nova daemon's startup scripts in Ubuntu needs to be slightly modified to run with our code: nova/nova- compute. log,--logfile /var/log/ nova/nova- compute. log,
s, > /var/log/