yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #87131
[Bug 1942413] Re: subport status is not updated when trunk or subport notification is received
Reviewed: https://review.opendev.org/c/openstack/neutron/+/807076
Committed: https://opendev.org/openstack/neutron/commit/101ccbaeb3c48d9757c276716098ee6e17e12fb8
Submitter: "Zuul (22348)"
Branch: master
commit 101ccbaeb3c48d9757c276716098ee6e17e12fb8
Author: Wenhai Li <liwenhai66@xxxxxxx>
Date: Thu Sep 2 17:01:38 2021 +0800
update subport status when trunk/subport create/delete is triggerred
When trunk or subport is created or deleted, notifications are sent. In
the meanwhile, subport status is not updated accordingly.
device_id device_owner and binding:host_id should be updated when
notifications are received.
In this patch, notifications are listened and subport status should be
updated when trunk/subport is created and subport is already added to
trunk:
device_id: <trunk_id>
device_owner: trunk:subport
binding:host_id: <parent port host_id>
When trunk/subport is deleted or subport is removed from trunk, subport
status should be updated:
device_id: None
device_owner: None
binding:host_id: None
Closes-Bug: #1942413
Change-Id: I0bdc5aabae0125926253b530fd0c6e79ba7bcbb9
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1942413
Title:
subport status is not updated when trunk or subport notification is
received
Status in neutron:
Fix Released
Bug description:
When trunk or subport is created or deleted, nofications are sent. In
the meanwhile, subport status is not updated according.
when trunk/subport is created and subport is already added to trunk,
subport status should be updated:
devicd_id:<trunk_id>
device_owner: trunk:subport
binding:host_id <parent_port host_id>
when trunk/subport is deleted or subport removed from trunk, subport
status should be updated:
device_id: None
device_onwer: None
binding_host_id: None
solution for this scenario is register for trunk/subport notification
and trigger subport update according to listening event and payload.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1942413/+subscriptions
References