changing from single vip to multiple vip's does not work

Bug #1827465 reported by Wouter van Bommel
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Percona Cluster Charm
Triaged
Wishlist
Unassigned

Bug Description

On an existing deployment updating the vip value to include multiple vips does not work. The result is that the newly added vip cannot be found in any configuration.

e.g. going from juju config mysql vip=10.20.40.26 to juju config mysql vip="10.20.40.26 10.20.43.26" will only keep the ip 10.20.40.26 and will not the 2nd ip.
Restart of pacemaker / corosync also did not change the situation.

crm config show, only returned the initially configured vip

Tags: bootstack
Revision history for this message
Andrea Ieri (aieri) wrote :

This might be a symptom caused by LP#1513889. It would be worth testing if a mysql cluster deployed with multiple vips from the start instantiates both or only one of them.

Revision history for this message
Dmitrii Shcherbakov (dmitriis) wrote :

AFAIK this charm never supported multiple VIPs because it was meant to serve on a single network only.

The difference with OpenStack charms is that it does not need to expose a public or admin API endpoint and also has only one hostname config for dns-ha.

The lack of support for changing VIPs in general is filed here https://bugs.launchpad.net/charm-hacluster/+bug/1513889 and here https://bugs.launchpad.net/charm-hacluster/+bug/1478980

Changed in charm-percona-cluster:
status: New → Triaged
importance: Undecided → Wishlist
Revision history for this message
Xav Paice (xavpaice) wrote :

Additional info: When I changed a vip, I expected that to cause a relation-changed and roll the new VIP through the shared-db relations - however, the config files in Nova didn't change at all.

Also; in the nova_api database, the cell_mappings table contains a database_connection field which has the connection string for the cell db - if the password or VIP changes, this field is unaffected.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.