.my.cnf should not contain LB VIP

Bug #1480987 reported by Paul Halmos
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Invalid
Undecided
Unassigned
Juno
Expired
Low
Unassigned
Trunk
Invalid
Undecided
Unassigned

Bug Description

The .my.cnf file gets created with the LB VIP for Galera in the host directive. This can cause confusion when you are checking Galera status or expecting to hit the MySQL instance on the container you are in. It should default to localhost and if you need to hit the VIP, you can pass -h VIP to mysql client.

Revision history for this message
Jesse Pretorius (jesse-pretorius) wrote :

MArked as invalid for master/kilo as the galera containers already point to 127.0.0.1 in those branches. This bug would be to backport that functionality to juno.

Changed in openstack-ansible:
status: New → Confirmed
Revision history for this message
Darren Birkett (darren-birkett) wrote :

The juno (10.1.11) deploys I am looking at have 127.0.0.1 as the host directive in the .my.cnf inside the galera containers, and the lb vip in the .my.cnf that exists on the physical hosts. Not sure this is a bug with the most recent juno.

Paul what version of juno are you seeing this behaviour on?

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for openstack-ansible juno because there has been no activity for 60 days.]

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.