fdb entries may contains inactive port

[Chengli Xu]

When the first port of an agent becomes active, or the agent is started within last 180 secs, l2 population mechanism driver will notify the agent with whole fdb entries (ports on all other agents). It doesn't filter inactive port (the status is BUILD/DOWN).

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/102543

[Romil Gupta (romilg)]

Hi Chengli Xu ,

Shall I take this bug and continue working on it before the review expires ?

Regards,
Romil

[Chengli Xu (superekcah)]

Hi Romil Gupta,

Sorry for my incomplete work, it's really appreciated if you can continue it.

[Romil Gupta (romilg)]

Thanks , I am assigning to myself and continuing from the same review ID.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/102543
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=f022caed48f7e0c2c97be22b90f4c3c5f24c6c31
Submitter: Jenkins
Branch: master

commit f022caed48f7e0c2c97be22b90f4c3c5f24c6c31
Author: Chengli XU <email address hidden>
Date: Wed Jun 25 22:26:04 2014 +0800

    l2-pop shouldn't notify agent about inactive ports

    When an agent starts, or the first port of an agent becomes active,
    l2 population mechanism driver will notify the agent of all ports on other agents.
    It should not notify about inactive ports.

    Basically, this patch-set is needed for fixing the bug 1332450.

    Co-Authored-By: Romil Gupta <email address hidden>

    Closes-Bug: #1334292
    Change-Id: Ifbbd7c4e22d4a6383a3c77a9d9ac9a37302c38c3