neutron.tests.tempest.api.test_routers.RoutersIpV6Test.test_router_interface_status failed
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | networking-ovn |
High
|
Lucas Alvares Gomes | ||
Bug Description
Tests below failed because ML2/OVN not setting router interface status to ACTIVE
neutron.
neutron.
Traceback (most recent call last):
File "/home/
utils.
File "/home/
raise exception
AssertionError
version Pike ovn HA setup.
| Eran Kuris (ekuris) wrote : | #1 |
| Numan Siddique (numansiddique) wrote : | #2 |
| tags: | added: ovn-upstream |
| Changed in networking-ovn: | |
| importance: | Undecided → High |
| Changed in networking-ovn: | |
| assignee: | nobody → Lucas Alvares Gomes (lucasagomes) |
Fix proposed to branch: master
Review: https:/
| Changed in networking-ovn: | |
| status: | New → In Progress |
Reviewed: https:/
Committed: https:/
Submitter: Zuul
Branch: master
commit 9d0bc3e93879c90
Author: Lucas Alvares Gomes <email address hidden>
Date: Wed Jun 6 14:49:21 2018 +0100
Fix: Router port always marked as DOWN
Router ports in OVN is never bound to a host given their decentralized
nature. For that reason, the code in Neutron core that change the status
of the ports (router ports are normal ports underneath) was ignoring the
OVN router ports.
This patch is forcing the status of those router ports to ACTIVE in
networking-ovn. A comment was left in the code in case we want to change
the core Neutron approach in the future.
This patch is also enabling two tempest tests that checks for this
router port status which were disabled before.
Change-Id: I5fd18e6e395a78
Closes-Bug: #1715126
| Changed in networking-ovn: | |
| status: | In Progress → Fix Released |
Fix proposed to branch: stable/queens
Review: https:/
| tags: | added: networking-ovn-proactive-backport-potential |
Reviewed: https:/
Committed: https:/
Submitter: Zuul
Branch: stable/queens
commit d93ac0454ec7738
Author: Lucas Alvares Gomes <email address hidden>
Date: Wed Jun 6 14:49:21 2018 +0100
Fix: Router port always marked as DOWN
Router ports in OVN is never bound to a host given their decentralized
nature. For that reason, the code in Neutron core that change the status
of the ports (router ports are normal ports underneath) was ignoring the
OVN router ports.
This patch is forcing the status of those router ports to ACTIVE in
networking-ovn. A comment was left in the code in case we want to change
the core Neutron approach in the future.
This patch is also enabling two tempest tests that checks for this
router port status which were disabled before.
Change-Id: I5fd18e6e395a78
Closes-Bug: #1715126
(cherry picked from commit 9d0bc3e93879c90
| tags: | added: in-stable-queens |
This issue was fixed in the openstack/
| Lucas Alvares Gomes (lucasagomes) wrote : | #8 |
I'm reopening the bug because the route ports on the gateway nodes (N/S traffic) are still being marked as DOWN.
| Changed in networking-ovn: | |
| status: | Fix Released → New |
Fix proposed to branch: master
Review: https:/
| Changed in networking-ovn: | |
| status: | New → In Progress |
Reviewed: https:/
Committed: https:/
Submitter: Zuul
Branch: master
commit 3d575d19b850134
Author: Lucas Alvares Gomes <email address hidden>
Date: Wed Aug 29 14:15:32 2018 +0100
Fix gateway's router port marked as DOWN
This patch is fixing a problem which left the external/gateway's router
port with status DOWN even after the port was bound to a chassis.
Since the Logical_Router_Port table in OVNNB does not have a "up" column
(like the Logical_Switch_Port table has) the status of those ports can
not be updpated based on it. Therefore, this patch uses the "chassis"
column for that. If the router port has the "chassis" column in OVNNB
database set, the binding and status ACTIVE will be set in Neutron
otherwise it status will be udpated to DOWN (if it's not DOWN yet).
Closes-Bug: #1715126
Change-Id: I91026204eae6df
| Changed in networking-ovn: | |
| status: | In Progress → Fix Released |
Fix proposed to branch: stable/rocky
Review: https:/
Fix proposed to branch: stable/queens
Review: https:/
Reviewed: https:/
Committed: https:/
Submitter: Zuul
Branch: stable/rocky
commit 6a423e51ee0940e
Author: Lucas Alvares Gomes <email address hidden>
Date: Wed Aug 29 14:15:32 2018 +0100
Fix gateway's router port marked as DOWN
This patch is fixing a problem which left the external/gateway's router
port with status DOWN even after the port was bound to a chassis.
Since the Logical_Router_Port table in OVNNB does not have a "up" column
(like the Logical_Switch_Port table has) the status of those ports can
not be updpated based on it. Therefore, this patch uses the "chassis"
column for that. If the router port has the "chassis" column in OVNNB
database set, the binding and status ACTIVE will be set in Neutron
otherwise it status will be udpated to DOWN (if it's not DOWN yet).
Closes-Bug: #1715126
Change-Id: I91026204eae6df
(cherry picked from commit 3d575d19b850134
| tags: | added: in-stable-rocky |
Reviewed: https:/
Committed: https:/
Submitter: Zuul
Branch: stable/queens
commit 27b6ea454b55817
Author: Lucas Alvares Gomes <email address hidden>
Date: Wed Aug 29 14:15:32 2018 +0100
Fix gateway's router port marked as DOWN
This patch is fixing a problem which left the external/gateway's router
port with status DOWN even after the port was bound to a chassis.
Since the Logical_Router_Port table in OVNNB does not have a "up" column
(like the Logical_Switch_Port table has) the status of those ports can
not be updpated based on it. Therefore, this patch uses the "chassis"
column for that. If the router port has the "chassis" column in OVNNB
database set, the binding and status ACTIVE will be set in Neutron
otherwise it status will be udpated to DOWN (if it's not DOWN yet).
Closes-Bug: #1715126
Change-Id: I91026204eae6df
(cherry picked from commit 3d575d19b850134
This issue was fixed in the openstack/
This issue was fixed in the openstack/
The below patches should fix this issue. There are under review now
https:/
https:/