Wrong status of trunk sub-port after seting binding_profile
Bug #1931583 reported by
Kamil Sambor
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron |
Fix Released
|
High
|
Kamil Sambor | ||
Bug Description
When sub-port was created (with OVN enabled) and event was process without binding profile this sub port will end forever in DOWN status
| description: | updated |
| Changed in neutron: | |
| status: | New → In Progress |
| assignee: | nobody → Kamil Sambor (ksambor) |
| tags: | added: ovn trunk |
| Changed in neutron: | |
| importance: | Undecided → High |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to neutron (master) | #1 |
| Changed in neutron: | |
| status: | In Progress → Fix Released |
| tags: | added: neutron-proactive-backport-potential |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/neutron 19.0.0.0rc1 | #2 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 6ada9124143f423
Author: Kamil Sambor <email address hidden>
Date: Tue Jun 8 14:56:01 2021 +0200
Set trunk sub-port when bind profile is created
Closes-Bug: #1931583
Change-Id: Ief14ef053023a0