yahoo-eng-team team mailing list archive

[Lynn <lynn.li@xxxxxx>]

Public bug reported:

When a VM host is created, a port is bound to this VM. Later on,
if an FIP agent gateway port gets paired with this VM host port,
it is bound to this VM. However, this FIP port's host and device
information remains empty as of today. Moreover, while performing
port disassociation on FIP table, this FIP port would get deleted
as it can't be recognized as a DVR serviceable port.

Host and device info needs to get migrated during the assigning process.

** Affects: neutron
     Importance: Undecided
     Assignee: Lynn (lynn-li)
         Status: In Progress

** Changed in: neutron
     Assignee: (unassigned) => Lynn (lynn-li)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1475096

Title:
  Host and device info need to get migrated to the VM host paired port
  that is found on the FIP table

Status in neutron:
  In Progress

Bug description:
  When a VM host is created, a port is bound to this VM. Later on,
  if an FIP agent gateway port gets paired with this VM host port,
  it is bound to this VM. However, this FIP port's host and device
  information remains empty as of today. Moreover, while performing
  port disassociation on FIP table, this FIP port would get deleted
  as it can't be recognized as a DVR serviceable port.

  Host and device info needs to get migrated during the assigning
  process.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1475096/+subscriptions