test_trunk_subport_lifecycle fails on subport down timeout
Bug #1707339 reported by
Armando Migliaccio
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Ihar Hrachyshka |
Bug Description
subport doesn't transition to DOWN state after trunk deletion
A failed run:
The agent log is filled with trace:
Error while processing VIF ports: OVSFWPortNotFound: Port 526e3ca9-
Incidentally, this port is a parent of a trunk port.
Now the trunk's OVSDB handler on the agent side relies on the OVS agent main loop to detect the port removal and let it notify the server to mark the logical port down. I wonder if these exceptions prevent that from happening.
Changed in neutron: | |
status: | New → Confirmed |
importance: | Undecided → High |
tags: | added: tru |
tags: |
added: trunk removed: tru |
Changed in neutron: | |
assignee: | Jakub Libosvar (libosvar) → Armando Migliaccio (armando-migliaccio) |
Changed in neutron: | |
status: | Confirmed → In Progress |
Changed in neutron: | |
assignee: | Armando Migliaccio (armando-migliaccio) → Jakub Libosvar (libosvar) |
Changed in neutron: | |
assignee: | Jakub Libosvar (libosvar) → Ihar Hrachyshka (ihar-hrachyshka) |
Changed in neutron: | |
milestone: | none → pike-rc1 |
To post a comment you must log in.
I'll look at it