openstack team mailing list archive

[Jay Pipes <jaypipes@xxxxxxxxx>]

On 07/24/2012 06:58 AM, Wolfgang Hennerbichler wrote:
> hi,
> 
> running openstack essex with vlan-networking:
> --network_manager=nova.network.manager.VlanManager
> --vlan_interface=bond0
> --public_interface=bridge_130
> --auto_assign_floating_ip=True
> 
> all works great except for floating ips. the problem is, that the
> floating ips are assigned to eth0 instead of bridge_130. I can't get a
> clue out of the logs:
> 
> 2012-07-24 11:24:02 DEBUG nova.service [-] public_interface : bridge_130
> from (pid=31192) wait /usr/lib/python2.7/dist-packages/nova/service.py:411
> 
> => so during startup it realizes that bridge_130 is the
> public-interface. great. But then the floating ip is assigned:
> 
> 2012-07-24 11:24:26 DEBUG nova.utils [-] Running cmd (subprocess): sudo
> nova-rootwrap ip addr add xx.xx.xx.129/32 dev eth0 from (pid=31192)
> execute /usr/lib/python2.7/dist-packages/nova/utils.py:219

Looking through the code, in the
nova.network.manager.FloatingIP.associate_floating_ip() call, I see this:

        interface = FLAGS.public_interface or floating_ip['interface']

on line 511 (in current HEAD of branch).

The only thing I could think of is that you created your floating IPs
before setting your FLAGS.public_interface?

Best,
-jay