yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #77871
[Bug 1822100] Re: Network Update if current provider net attribure key/value pair in request
Reviewed: https://review.openstack.org/648522
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=20743350b9b40fd7a2cff074bb2c877ea36c5914
Submitter: Zuul
Branch: master
commit 20743350b9b40fd7a2cff074bb2c877ea36c5914
Author: Rodolfo Alonso Hernandez <ralonsoh@xxxxxxxxxx>
Date: Tue Apr 2 16:57:17 2019 +0100
Allow provider net attr in update if no change
If provider net attributes are in update request body,
do an additional check to see if the values are actually
different. Only raise exception if values are different.
Closes-Bug: #1822100
Co-Authored-By: Rodolfo Alonso Hernandez <ralonsoh@xxxxxxxxxx>
Change-Id: I4ac11299375d1d3a7d2013f1fdc1742920d884a9
** 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/1822100
Title:
Network Update if current provider net attribure key/value pair in
request
Status in neutron:
Fix Released
Bug description:
Network initially created with:
{'network': {'provider:physical_network': 'external',
'provider:network_type': 'flat'}
Network is then updated with:
{'network': {'provider:physical_network': 'external',
'provider:network_type': 'flat',
'mtu': 9000}
The net_data is checked for provider attribute's being updated[1], this raises the exception despite the actual values of provider net attributes did not change.
[1] https://github.com/openstack/neutron/blob/af130e79cbe5d12b7c9f9f4dcbcdc8d972bfcfd4/neutron/plugins/ml2/plugin.py#L988
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1822100/+subscriptions
References