[Bug 1459046] Re: nova-* services do not start if rsyslog is not yet started

[Martin Pitt]

This is apparently an SRU fix for trusty. Does that also affect later
releases? In particular, does it affect vivid/wily, as we don't use
upstart there but systemd? In particular, these would need an
After=syslog.service, is that the case? If not, this needs to be fixed
as well, and as per the SRU rules a bug has to be fixed in the
development series first. Thanks!

** Also affects: nova (Ubuntu Trusty)
   Importance: Undecided
       Status: New

** Changed in: nova (Ubuntu Trusty)
       Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1459046

Title:
  nova-* services do not start if rsyslog is not yet started

Status in nova package in Ubuntu:
  In Progress
Status in nova source package in Trusty:
  In Progress

Bug description:
  [Impact]

   * Nova services fail to start because they cannot connect to rsyslog

  [Test Case]

   * Set user_syslog to True in nova.conf, stop rsyslog service and
  restart nova services.

  [Regression Potential]

   * None

  
  When nova services log to syslog, we should make sure the dependency on the upstart jobs is set prior to the nova-* services start.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1459046/+subscriptions