Adding tiers on rVPC leads to master/master state

[remibergsma]

When adding tiers, through UI with some time in between, the routers end up in master/master state because their keepalived.conf is configured differently (with another device) so they never get each others messages and think they're alone.

Router1:

global_defs {
    router_id r-4994-VM
}

vrrp_script heartbeat {
    script "/ramdisk/rrouter/heartbeat.sh"
    interval 5
}

vrrp_instance inside_network {
    state EQUAL
    interface eth2
    virtual_router_id 51
    nopreempt

    advert_int 2
    authentication {
        auth_type AH
        auth_pass 2460884277967388862553233224158858301399005540157527002917751881683621535426194086689150791461426972960290099751568683025981284206686699606989348185549356
    }

    virtual_ipaddress {
        10.4.4.1/24 brd 10.4.4.255 dev eth5
        10.4.3.1/24 brd 10.4.3.255 dev eth4
        10.4.2.1/24 brd 10.4.2.255 dev eth3
        10.4.1.1/24 brd 10.4.1.255 dev eth2
    }

    track_script {
        heartbeat
    }

    !That's the correct path of the master.py file.
    notify_backup "/opt/cloud/bin/master.py --backup"
    notify_master "/opt/cloud/bin/master.py --master"
    notify_fault "/opt/cloud/bin/master.py --fault"

Router2:

global_defs {
    router_id r-4992-VM
}

vrrp_script heartbeat {
    script "/ramdisk/rrouter/heartbeat.sh"
    interval 5
}

vrrp_instance inside_network {
    state EQUAL
    interface eth3
    virtual_router_id 51
    nopreempt

    advert_int 2
    authentication {
        auth_type AH
        auth_pass 2460884277967388862553233224158858301399005540157527002917751881683621535426194086689150791461426972960290099751568683025981284206686699606989348185549356
    }

    virtual_ipaddress {
        10.4.4.1/24 brd 10.4.4.255 dev eth5
        10.4.3.1/24 brd 10.4.3.255 dev eth4
        10.4.2.1/24 brd 10.4.2.255 dev eth3
    }

    track_script {
        heartbeat
    }

    !That's the correct path of the master.py file.
    notify_backup "/opt/cloud/bin/master.py --backup"
    notify_master "/opt/cloud/bin/master.py --master"
    notify_fault "/opt/cloud/bin/master.py --fault"

Interface eht2 seems not to be there on one of the routers. After running cloud-early-config it worked fine.

I've seen this happening before (it pages) but it's not clear when it happens. Should we have more info we can add it here.