dhcp port binding fail

Bug #1348589 reported by Xurong Yang
42
This bug affects 7 people
Affects Status Importance Assigned to Milestone
neutron
In Progress
Medium
vikas choudhary

Bug Description

When creating a subnet while ovs agent is down, the subnet and the corresponding dhcp port are created successfully. However, the vif_type of the port is "binding_failed" and the segment is NULL so when ovs agent restarts, it won't set the vlan tag of the dhcp port and there is no chance for the vif_type to be set again.

I think we need a mechanism the validate the dhcp port so dhcp agent can recreate or update the port when the vif_type is invalid.

Tags: ovs ml2
Xurong Yang (idopra)
Changed in neutron:
assignee: nobody → Xurong Yang (idopra)
Changed in neutron:
importance: Undecided → Medium
tags: added: ml2 ovs
Revision history for this message
Eugene Nikanorov (enikanorov) wrote :

Removing assignee due to lack of activity

Changed in neutron:
assignee: Xurong Yang (idopra) → nobody
Romil Gupta (romilg)
Changed in neutron:
assignee: nobody → Romil Gupta (romilg)
Revision history for this message
Romil Gupta (romilg) wrote :

I am trying to reproduce this and fix accordingly.

Revision history for this message
ratalevolamena (chris-techno1307) wrote :

how to fix this bug???

Revision history for this message
songqianxia (songlihui1947) wrote :

Will you please share your ideas, what you will do for it?

Revision history for this message
vikas choudhary (choudharyvikas16) wrote :

Hi..any body working on this bug?

Revision history for this message
vikas choudhary (choudharyvikas16) wrote :

As there is no activity on this since months, I am assigning it to myself.

Changed in neutron:
assignee: Romil Gupta (romilg) → vikas choudhary (choudharyvikas16)
Changed in neutron:
status: New → In Progress
Revision history for this message
vikas choudhary (choudharyvikas16) wrote :

I want to discuss on https://bugs.launchpad.net/neutron/+bug/1348589.This is there for more than a year and no discussion i could find on this.

Scenario:
ovs-agent is down and then a network and subnet under this newly created network are created using cli. No error visible to user, but following irregularities are found.

Discrepancies:
1. neutron port-show <dhcp-port> shows:
     binding:vif_type | binding_failed
2. Running "ovs-ofctl dump-flows br-tun", no of-flow got added
3. Running "ovs-vsctl show br-int", no tag for dhcp-port.

neutron db will have all the attributes required to retry vif binding.My query is when should we trigger this rebinding.Two approaches i could think of are:
1> At neutron server restart, for all ports with vif_type as "binding_failed" plugins/ml2/drivers/mech_agent.bind_port can be invoked as a sync up activity.

2> In neutron port update api, http://developer.openstack.org/api-ref-networking-v2-ext.html , could be enhanced to receive vif binding related options also and then eventually plugins/ml2/drivers/mech_agent.bind_port can be invoked.Corresponding changes will be made to 'port update cli' also.

Please suggest.

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.