[Bug 1089711] [NEW] nova.conf unreadable is hard to diagnose

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When nova.conf is unreadable (due to permissions), nova services won't
start. However this is difficult to diagnose because there is no error
given from the upstart script, and there is no entry whatsoever in the
service's logs (/var/log/nova-scheduler.log for example). Instead the
only clue shows up in syslog:

Dec 12 22:05:50 z2 kernel: [  390.442678] init: nova-scheduler main
process (23171) terminated with status 143

It would be much better if this error said something to the effect of
"could not read config file /etc/nova/nova.conf"

I'm seeing this on Folsom:

root at z2:/var/log/nova# dpkg -l | grep nova
ii  nova-api                         2012.2-0ubuntu5~cloud0.1         OpenStack Compute - API frontend
ii  nova-cert                        2012.2-0ubuntu5~cloud0.1         OpenStack Compute - certificate management
ii  nova-common                      2012.2-0ubuntu5~cloud0.1         OpenStack Compute - common files
ii  nova-doc                         2012.2-0ubuntu5~cloud0.1         OpenStack Compute - documentation
ii  nova-network                     2012.2-0ubuntu5~cloud0.1         OpenStack Compute - Network manager
ii  nova-scheduler                   2012.2-0ubuntu5~cloud0.1         OpenStack Compute - virtual machine scheduler

** Affects: nova (Ubuntu)
     Importance: Undecided
         Status: New

-- 
nova.conf unreadable is hard to diagnose
https://bugs.launchpad.net/bugs/1089711
You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu.