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.
Reviewed: https:/ /review. openstack. org/457757 /git.openstack. org/cgit/ openstack/ charm-nova- cloud-controlle r/commit/ ?id=e94f7882cb7 603723f993600b0 44cf9dcf544760
Committed: https:/
Submitter: Jenkins
Branch: master
commit e94f7882cb76037 23f993600b044cf 9dcf544760
Author: David Ames <email address hidden>
Date: Tue Apr 18 10:56:09 2017 -0700
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 f7a8b0f12c8f0a8 cf8f78595b6
Change-Id: Ifd4e975d9abbb9