need to handle/prohibit case where users specify both internal and external vip to be the same

Bug #1486393 reported by Vedamurthy Joshi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R2.20
New
High
Sanju Abraham
Trunk
New
High
Sanju Abraham

Bug Description

R2.20 Ubuntu 14.04 Build 79

When we have a HA-enabled cluster with only one network, (i.e. without control/data section in testbed.py), and the users specifiy the env.ha with both internal and external vip to be same, it is seen that it causes broadcast storm in the network(pkts of arp/vrrp are flooded in the network) :

env.ha = {
    'internal_vip' : '10.204.216.184',
    'external_vip' : '10.204.216.184',
}

During provisioning, We either need to handle this or throw errors

Tags: ha
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.