nova-network: br100 is assigned two IPs, original is lost.

Bug #855971 reported by Adam Gandelman
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Invalid
Undecided
Unassigned

Bug Description

Using FlatDHCPManager on a single NIC, single network setup, I've been using eth0 (which already has IP 10.55.55.3) as the bridge_interface for br100. To avoid conflicts, I manually reserve fixed_ips for hosts. (10.55.55.0-10.55.55.18 end up as reserved in fixed_ips). Using nova-network 2011.3~rc~20110909.r1155-0ubuntu1 , all works well. br100 is created, inherits the IP of eth0 and serves DHCP with unreserve and non-conflicting addresses. This is a testing environment.

Using milestone-proposed / 2012.1~e1~20110921.1611-0ubuntu0ppa1~oneiric1, the bridge seems to first inheirt the original IP of the interface but then is assigned another IP, which I assume is coming from the unrresrved pool of fixed_ips.

corresponding parts of nova-network.log attached.

Revision history for this message
Adam Gandelman (gandelman-a) wrote :
Changed in nova:
status: New → Invalid
Revision history for this message
Vish Ishaya (vishvananda) wrote :

Thiis is expected behavior. In HA mode each host needs to be assigned an ip to gateway for its vms. If you want to manually reserve an ip for a host, it is insufficient to simply set it to reserved. You will need to manually associate it with the host by setting the host field in the fixed_ips table.

Something like:

mysql -h $MYSQL_HOST -u $MYSQL_USER -p $MYSQL_PASS $MYSQL_DB -e "UPDATE fixed_ips SET host=`hostname` WHERE address='$MY_IP'"

should be sufficient.

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.