Bug 1469366 - Port status should reflect the actual status of the port
Summary: Port status should reflect the actual status of the port
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-networking-odl
Version: 11.0 (Ocata)
Hardware: Unspecified
OS: Unspecified
Target Milestone: beta
: 12.0 (Pike)
Assignee: Josh Hershberg
QA Contact: Itzik Brown
Depends On: 1414298
TreeView+ depends on / blocked
Reported: 2017-07-11 06:37 UTC by Itzik Brown
Modified: 2018-10-18 07:24 UTC (History)
3 users (show)

Fixed In Version: python-networking-odl-11.0.0-0.20170707060026.5ccb48f.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-12-13 21:40:04 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
OpenStack gerrit 465462 0 None MERGED Utilty for determining ODL neutron features 2020-05-25 19:20:41 UTC
OpenStack gerrit 465463 0 None MERGED Retrieve and process port status updates from ODL 2020-05-25 19:20:41 UTC
Red Hat Product Errata RHEA-2017:3462 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-16 01:43:25 UTC

Description Itzik Brown 2017-07-11 06:37:39 UTC
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:

Comment 1 Mike Kolesnik 2017-07-11 06:45:49 UTC
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).

Comment 4 Itzik Brown 2017-08-08 08:27:53 UTC
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

Comment 7 errata-xmlrpc 2017-12-13 21:40:04 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.