yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #37738
[Bug 1459046] Re: [SRU] nova-* services do not start if rsyslog is not yet started
** Changed in: nova
Status: Fix Committed => Fix Released
** Changed in: nova
Milestone: None => liberty-3
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1459046
Title:
[SRU] nova-* services do not start if rsyslog is not yet started
Status in ubuntu-cloud-archive:
Confirmed
Status in ubuntu-cloud-archive icehouse series:
Fix Released
Status in ubuntu-cloud-archive juno series:
In Progress
Status in ubuntu-cloud-archive kilo series:
Confirmed
Status in ubuntu-cloud-archive liberty series:
Fix Released
Status in OpenStack Compute (nova):
Fix Released
Status in oslo.log:
Fix Released
Status in nova package in Ubuntu:
Invalid
Status in python-oslo.log package in Ubuntu:
Fix Released
Status in nova source package in Trusty:
Fix Released
Status in python-oslo.log source package in Trusty:
Invalid
Status in nova source package in Utopic:
Won't Fix
Status in python-oslo.log source package in Utopic:
Invalid
Status in nova source package in Vivid:
Invalid
Status in python-oslo.log source package in Vivid:
Confirmed
Status in nova source package in Wily:
Invalid
Status in python-oslo.log source package in Wily:
Fix Released
Bug description:
[Impact]
* If Nova services are configured to log to syslog (use_syslog=True) they
will currently fail with ECONNREFUSED if they cannot connect to syslog.
This patch adds support for allowing nova to retry connecting a
configurable number of times before print an error message and continuing
with startup.
[Test Case]
* Configure nova with use_syslog=True in nova.conf, stop rsyslog service and
restart nova services. Check that upstart nova logs to see retries
occurring then start rsyslog and observe connection succeed and
nova-compute startup.
[Regression Potential]
* None
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1459046/+subscriptions