Comment 7 for bug 1641464

I just ran a new deployment, paying attention to the juju debug-log this time.

Following the verification of *MOST* packages (89/99), the process hangs. No indication that the config-changed hook has executed at all.

Checking on the compute node:
[root@zs93k23 ~]# systemctl status openstack-nova-compute.service
● openstack-nova-compute.service - OpenStack Nova Compute Server
   Loaded: loaded (/usr/lib/systemd/system/openstack-nova-compute.service; enabled; vendor preset: disabled)
   Active: activating (start) since Tue 2016-11-29 17:11:56 EST; 2min 6s ago
 Main PID: 63372 (nova-compute)
   CGroup: /system.slice/openstack-nova-compute.service
           └─63372 /usr/bin/python2 /usr/bin/nova-compute

Nov 29 17:11:56 zs93k23 systemd[1]: Starting OpenStack Nova Compute Server...

Running systemctl stop on the service, I immediately notice the unit.nova-compute-proxy/0.config-changed hook fire.

The behaviour is different this time though -- the service stays stopped and I had to start it manually -- it did start up normally!

juju debug-log with a few notes: http://paste.ubuntu.com/23555412/