nova-cloud-controller unit doesn' start when upgrading to 2.8.2 model
Bug #1890399 reported by
Mark Cave-Ayland
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Nova Cloud Controller Charm |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
I recently upgraded our openstack from 2.6 to the latest 2.8.2 model and found that the nova-cloud-
Investigating with help from members of the #openstack-charms IRC channel it was found that all of the systemd services for the cloud controller unit had been masked. With this knowledge I was able to manually unmask, enable and start all of the nova, memcached, haproxy and apache2 services which brought the unit back to life.
gnuoy suggested that it may be because the install hook was run as part of running "juju upgrade-charm" as part of the upgrade to 2.8.
To post a comment you must log in.
Here is the original output from /var/log/ juju/unit- nova-cloud- controller. log after the 2.8 upgrade when the unit failed to start:
2020-08-05 06:53:33 INFO juju-log Registered config file: /etc/nova/nova.conf api-paste. ini vendor_ data.json haproxy. cfg sites-available /openstack_ https_frontend. conf ports.conf sites-enabled/ wsgi-api- os-compute. conf sites-enabled/ wsgi-placement- api.conf sites-enabled/ wsgi-openstack- metadata. conf haproxy.
2020-08-05 06:53:33 INFO juju-log Registered config file: /etc/nova/
2020-08-05 06:53:33 INFO juju-log Registered config file: /etc/nova/
2020-08-05 06:53:33 INFO juju-log Registered config file: /etc/haproxy/
2020-08-05 06:53:33 INFO juju-log Registered config file: /etc/apache2/
2020-08-05 06:53:33 INFO juju-log Registered config file: /etc/apache2/
2020-08-05 06:53:33 INFO juju-log Registered config file: /etc/memcached.conf
2020-08-05 06:53:33 INFO juju-log Registered config file: /etc/apache2/
2020-08-05 06:53:33 INFO juju-log Registered config file: /etc/apache2/
2020-08-05 06:53:33 INFO juju-log Registered config file: /etc/apache2/
2020-08-05 06:53:33 DEBUG juju-log Hardening function 'update_status'
2020-08-05 06:53:33 DEBUG juju-log No hardening applied to 'update_status'
2020-08-05 06:53:33 INFO juju-log Updating status.
2020-08-05 06:53:33 INFO juju-log Registered config file:
2020-08-05 06:53:33 DEBUG juju-log 0 section(s) found
2020-08-05 06:53:34 DEBUG juju-log Generating template context for amqp
2020-08-05 06:53:34 DEBUG update-status ERROR no relation id specified
2020-08-05 06:53:34 DEBUG juju-log Generating template context for image-service.
2020-08-05 06:53:34 DEBUG juju-log 0 section(s) found
2020-08-05 06:53:34 INFO juju-log HAProxy context is incomplete, this unit has no peers.
2020-08-05 06:53:34 DEBUG juju-log Generating template context for identity-service
2020-08-05 06:53:34 INFO juju-log Generating template context from neutron api relation
2020-08-05 06:53:34 DEBUG juju-log Generating template context for identity-service
2020-08-05 06:53:35 DEBUG juju-log Ensuring haproxy enabled in /etc/default/
2020-08-05 06:53:35 INFO juju-log HAProxy context is incomplete, this unit has no peers.
2020-08-05 06:53:35 DEBUG juju-log 0 section(s) found
2020-08-05 06:53:35 INFO juju-log HAProxy context is incomplete, this unit has no peers.
2020-08-05 06:53:35 INFO juju-log HAProxy context is incomplete, this unit has no peers.
2020-08-05 06:53:35 INFO juju-log HAProxy context is incomplete, this unit has no peers.
2020-08-05 06:53:35 INFO juju-log Generating template context from neutron api relation
2020-08-05 06:53:35 DEBUG update-status inactive
2020-08-05 06:53:35 DEBUG update-status inactive
2020-08-05 06:53:35 DEBUG update-status inactive
2020-08-05 06:53:35 DEBUG update-status inactive
2020-08-05 06:53:35 DEBUG update-status active
2020-08-05 06:53:35 DEBUG update-status inactive
2020-08-05 06:53:35 DEBUG update-status active