charm-neutron-api/unit_tests
David Ames 43e4f2124f Avoid shared-db change when using access-network
When the percona-cluster charm sets an access-network but the default
unit-get address is not on that network extra shared-db relations get
executed. This is specifically a problem when running upgrades and
trying to avoid API downtime.

The root cause is that the access-network is not checked until the
SharedDBContext is consulted. But then db_joined function will
change it back to the wrong ip on subsequent runs.

This change adds a check for access-network on the relation during
the db_joined function and pushes IP selection off to get_relation_ip.

Charm helpers sync to pull in changes to get_relation_ip.

Partial-bug: #1677647

Change-Id: I20f35dd7a12315ef61939feb5199680db128bc0b
2017-04-26 10:04:11 -07:00
..
__init__.py Re-license charm as Apache-2.0 2016-07-03 17:47:52 +01:00
test_actions_git_reinstall.py Re-license charm as Apache-2.0 2016-07-03 17:47:52 +01:00
test_actions_openstack_upgrade.py Re-license charm as Apache-2.0 2016-07-03 17:47:52 +01:00
test_actions.py Re-license charm as Apache-2.0 2016-07-03 17:47:52 +01:00
test_neutron_api_context.py Avoid shared-db change when using access-network 2017-04-26 10:04:11 -07:00
test_neutron_api_hooks.py Avoid shared-db change when using access-network 2017-04-26 10:04:11 -07:00
test_neutron_api_utils.py Fix alphanumeric comparisons for openstack and ubuntu releases 2017-03-28 17:30:14 +01:00
test_utils.py Re-license charm as Apache-2.0 2016-07-03 17:47:52 +01:00