Billy Olsen 231a0f1459 Drop placement endpoints from relation in train+ ... When a cloud is deployed earlier than the Train release, the placement service is provided by nova-cloud-controller. As part of an upgrade to Train, the new placement service is added and updates the placement endpoint in the service catalog. The nova-cloud-controller charm no longer advertises the placement service URL, but because the data exists on the relation until removed, the service catalog changes the placement URL to the placement endpoints advertised from nova-cloud-controller. Fix this by explicitly removing the placement service URLs when the placement service is not provided by nova-cloud-controller. Change-Id: Ibb3b1429820a4188fe3d2c1142c295c0de4ee24e Closes-Bug: #1928992		2021-07-27 11:23:59 -07:00
..
__init__.py	Sync libraries & common files prior to freeze	2020-09-28 09:37:24 +01:00
test_actions_openstack_upgrade.py	Ensure placement charm related before Train upgrade	2019-10-18 13:52:15 +00:00
test_actions.py	Add sync-compute-availability-zones Juju action	2021-04-22 19:54:36 -07:00
test_nova_cc_contexts.py	Updates for testing period for 20.01 release	2021-01-18 19:05:18 +00:00
test_nova_cc_hooks.py	Set cross_az_attach setting on cloud-compute relation	2021-04-13 11:38:56 -07:00
test_nova_cc_utils.py	Drop placement endpoints from relation in train+	2021-07-27 11:23:59 -07:00
test_utils.py	Switch the charm to support py3	2018-10-18 15:43:03 +01:00