Merge lp:~gnuoy/charms/trusty/nova-cloud-controller/fix-db-migrations into lp:~openstack-charmers-archive/charms/trusty/nova-cloud-controller/next
Proposed by
Liam Young
Status: | Merged |
---|---|
Merged at revision: | 123 |
Proposed branch: | lp:~gnuoy/charms/trusty/nova-cloud-controller/fix-db-migrations |
Merge into: | lp:~openstack-charmers-archive/charms/trusty/nova-cloud-controller/next |
Diff against target: |
94 lines (+36/-34) 2 files modified
hooks/nova_cc_utils.py (+35/-33) unit_tests/test_nova_cc_utils.py (+1/-1) |
To merge this branch: | bzr merge lp:~gnuoy/charms/trusty/nova-cloud-controller/fix-db-migrations |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
James Page | Approve | ||
Review via email: mp+239389@code.launchpad.net |
Description of the change
If the neutron-api relation was present then this charm was dropping management of neutron which included the neutron config files. Unfortunately those files are needed to run the db migrations. This mp stops the services associated with the neutron files from being managed but reinstates the management of the files themselves.
I have tested by doing a deployment and omitting the nova-cc <-> mysql relation. Then, adding the relation in and checking that a db migration is run correctly and that the neutron-server is restarted on the neutron-api server
To post a comment you must log in.
UOSCI bot says: controller- next for gnuoy mp239389
charm_lint_check #742 nova-cloud-
LINT OK: believed to pass, but you should confirm results
LINT Results (max last 4 lines) from jenkins/ workspace/ charm_lint_ check/make- lint.742: client- timeout has no default value
/var/lib/
I: config.yaml: option haproxy-
I: config.yaml: option ssl_cert has no default value
I: config.yaml: option nvp-l3-uuid has no default value
I: config.yaml: option os-internal-network has no default value
Full lint output: http:// paste.ubuntu. com/8641966/ 10.98.191. 181:8080/ job/charm_ lint_check/ 742/
Build: http://