Description of problem: The port status is ACTIVE even when it's attached to an instance and the instance is not up. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create a port 2. Launch an instance with the above port attached 3. Watch that the port status is active even that the instance is not running. Actual results: Expected results: Additional info:
I would say that after step 1 you can already see the port is in status ACTIVE even though its not really provisioned yet. The actual problem is that it's immediately set to active instead of when it's provisioned on the network as is in vanilla Neutron. Also please notice it's not expected of the port to change status after it changes to ACTIVE (per current Neutron behavior).
https://git.opendaylight.org/gerrit/52173 https://git.opendaylight.org/gerrit/53216 https://git.opendaylight.org/gerrit/51554 https://git.opendaylight.org/gerrit/55854 https://git.opendaylight.org/gerrit/56067 https://git.opendaylight.org/gerrit/55856 https://review.openstack.org/#/c/465462/ https://review.openstack.org/465463 https://review.openstack.org/467645 https://review.openstack.org/479588 https://review.openstack.org/483199
Checked that that the instance is not in 'active running' state before the port status is active. Checked with python-networking-odl-11.0.0-0.20170721155128.a047729.el7ost.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:3462