Nova creates duplicate Neutron ports on instance reschedule

Bug #1617291 reported by Alexey I. Froloff
32
This bug affects 7 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Confirmed
Medium
Sivasathurappan Radhakrishnan

Bug Description

Neutron network driver in Nova creates new port unless port_id is specified. If instance is rescheduled for some reason, these ports should either be deleted or re-used on next try. Reuse doesn't happen because Neutron driver in Nova creates new port unless port_id is specified. New port is then created and instance gets multiple ports (one for each reschedule attempt) while only one is "correct".

This happens because on reschedule network cleanup only happens if virt driver tells to deallocate_networks_on_reschedule (which is only true for Ironic driver).

Tags: neutron
Rajesh Tailor (ratailor)
Changed in nova:
assignee: nobody → Rajesh Tailor (ratailor)
Revision history for this message
Sivasathurappan Radhakrishnan (siva-radhakrishnan) wrote :

@Rajesh Tailor: are you still working on this bug ?

Rajesh Tailor (ratailor)
Changed in nova:
assignee: Rajesh Tailor (ratailor) → nobody
Changed in nova:
assignee: nobody → Sivasathurappan Radhakrishnan (siva-radhakrishnan)
sandeep nandal (nandal)
Changed in nova:
importance: Undecided → Medium
Changed in nova:
status: New → Confirmed
tags: added: neutron
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.