Sorry, I just noticed the issues around stable/mitaka. The provisioning
blocks were clearly not the only cause of this behavior because they
didn't exist in Mitaka.
** Changed in: neutron
Status: Fix Released => Confirmed
** Changed in: neutron
Assignee: Kevin Benton (kevinbenton) => (unassigned)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1590845
Title:
Router interfaces report being in BUILD state - l3ha vrrp+LinuxBridge
Status in neutron:
Confirmed
Bug description:
I'm running a Liberty environment with two network hosts using the L3HA VRRP
driver.
I also have L2pop on and am using the ML2 LinuxBridge driver.
When we programmatically attach subnets and/or ports to routers(we attach 1
interface every 60 seconds), some report back stuck in the BUILD state. Take
this interface, for example:
neutron port-show 98b55b89-a002-496f-a5d4-8de598613da8
+-----------------------+--------------------------------------------------------------------------------------------------------------+
| Field | Value
|
+-----------------------+--------------------------------------------------------------------------------------------------------------+
| admin_state_up | True
|
| allowed_address_pairs |
|
| binding:host_id | dn3usoskctl03_neutron_agents_container-e64e37d6
|
| binding:profile | {}
|
| binding:vif_details | {"port_filter": true}
|
| binding:vif_type | bridge
|
| binding:vnic_type | normal
|
| device_id | 5838c5de-e87a-4e5e-b61f-a3f068fa7726
|
| device_owner | network:router_interface
|
| dns_assignment | {"hostname": "host-10-169-160-1", "ip_address":
"10.169.160.1", "fqdn": "host-10-169-160-1.openstacklocal."} |
| dns_name |
|
| extra_dhcp_opts |
|
| fixed_ips | {"subnet_id":
"bc3a8d37-6cd7-4d57-b0c9-2b35743b0a0b", "ip_address": "10.169.160.1"}
|
| id | 98b55b89-a002-496f-a5d4-8de598613da8
|
| mac_address | fa:16:3e:b9:7a:1d
|
| name |
|
| network_id | 535c3336-202c-4dab-b517-2232c4ce1481
|
| security_groups |
|
| status | BUILD
|
| tenant_id | 3ccf712795c44edcbc8ffcc331a59853
|
+-----------------------+--------------------------------------------------------------------------------------------------------------+
It's reporting itself in the BUILD state, but when I check the router
namespace, it's linux networking component counter part seems to be
functioning just fine:
8: qr-98b55b89-a0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
pfifo_fast state UP group default qlen 1000
link/ether fa:16:3e:b9:7a:1d brd ff:ff:ff:ff:ff:ff
inet 10.169.160.1/23 scope global qr-98b55b89-a0
valid_lft forever preferred_lft forever
inet6 fe80::f816:3eff:feb9:7a1d/64 scope link
valid_lft forever preferred_lft forever
I can even ping the address with no problem once i open up the
security group rules.
Note: The problem doesn't appear when L3HA is turned off. Only when
L3HA with VRRP keepalived driver is being used.
Where would be a good place to start debugging this?
Thanks!
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1590845/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
