yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1459046@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package nova - 1:2014.1.5-0ubuntu1.2

---------------
nova (1:2014.1.5-0ubuntu1.2) trusty; urgency=medium

  * Add rsyslog retry support (LP: #1459046)
    - d/p/add-support-for-syslog-connect-retries.patch
  * Add vm clean shutdown support (LP: #1196924)
    - d/p/clean-shutdown.patch

 -- Edward Hope-Morley <edward.hope-morley@xxxxxxxxxxxxx>  Thu, 16 Jul
2015 11:55:57 +0100

** Changed in: nova (Ubuntu Trusty)
       Status: Fix Committed => Fix Released

-- 
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:
  In Progress
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):
  New
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