Comment 1 for bug 1498605

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

I did a fresh deploy and mysql was the only service with an incorrect netmask for the vip ip (in the output of ip addr):
19: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:16:3e:93:77:4b brd ff:ff:ff:ff:ff:ff
    inet 10.96.8.45/16 brd 10.96.255.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet 10.96.10.9/24 brd 10.96.10.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::216:3eff:fe93:774b/64 scope link
       valid_lft forever preferred_lft forever

Note that the vip (10.9) also has the same scope as the other IP, instead of "scope global secondary" like the other services. For example:
15: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:16:3e:27:ec:c4 brd ff:ff:ff:ff:ff:ff
    inet 10.96.8.143/16 brd 10.96.255.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet 10.96.10.108/16 brd 10.96.255.255 scope global secondary eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::216:3eff:fe27:ecc4/64 scope link
       valid_lft forever preferred_lft forever