yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #57394
[Bug 1630410] [NEW] fixed_ips list out of order
Public bug reported:
Change [1], led to failures like [2], in that the order of fixed_ips is
no longer preserved between POST and GET requests. This was taken care
for some other attributes of the Port resource like allowed address
pairs, but not all.
Even though the API is lax about the order of specific attributes, we
should attempt to restore the old behavior to avoid more damaging side
effects in clients that are assuming the list be returned in the order
in which fixed IPs are created.
[1] https://review.openstack.org/#/c/373582
[2] https://www.google.com/url?q=http%3A%2F%2Flogs.openstack.org%2F63%2F377163%2F4%2Fcheck%2Fgate-shade-dsvm-functional-neutron%2Fe621e3d%2Fconsole.html&sa=D&sntz=1&usg=AFQjCNG3xbH0QxdjxrkuAseWtPGpUm4heg
** Affects: neutron
Importance: Medium
Assignee: Kevin Benton (kevinbenton)
Status: Confirmed
** Tags: newton-backport-potential
** Changed in: neutron
Importance: Undecided => Medium
** Changed in: neutron
Status: New => Confirmed
** Changed in: neutron
Assignee: (unassigned) => Kevin Benton (kevinbenton)
** Changed in: neutron
Milestone: None => ocata-1
** Tags added: newton-backport-potential
** Description changed:
Change [1], led to failures like [2], in that the order of fixed_ips is
no longer preserved between POST and GET requests. This was taken care
- of some some other attributes of the Port resources like allowed address
- pairs, but not for all.
+ for some other attributes of the Port resource like allowed address
+ pairs, but not all.
Even though the API is lax about the order of specific attributes, we
should attempt at restoring the old behavior to avoid more damaging side
effects in clients that are assuming the list be returned in the order
in which fixed IPs are created.
[1] https://review.openstack.org/#/c/373582
[2] https://www.google.com/url?q=http%3A%2F%2Flogs.openstack.org%2F63%2F377163%2F4%2Fcheck%2Fgate-shade-dsvm-functional-neutron%2Fe621e3d%2Fconsole.html&sa=D&sntz=1&usg=AFQjCNG3xbH0QxdjxrkuAseWtPGpUm4heg
** Description changed:
Change [1], led to failures like [2], in that the order of fixed_ips is
no longer preserved between POST and GET requests. This was taken care
for some other attributes of the Port resource like allowed address
pairs, but not all.
Even though the API is lax about the order of specific attributes, we
- should attempt at restoring the old behavior to avoid more damaging side
+ should attempt to restore the old behavior to avoid more damaging side
effects in clients that are assuming the list be returned in the order
in which fixed IPs are created.
[1] https://review.openstack.org/#/c/373582
[2] https://www.google.com/url?q=http%3A%2F%2Flogs.openstack.org%2F63%2F377163%2F4%2Fcheck%2Fgate-shade-dsvm-functional-neutron%2Fe621e3d%2Fconsole.html&sa=D&sntz=1&usg=AFQjCNG3xbH0QxdjxrkuAseWtPGpUm4heg
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1630410
Title:
fixed_ips list out of order
Status in neutron:
Confirmed
Bug description:
Change [1], led to failures like [2], in that the order of fixed_ips
is no longer preserved between POST and GET requests. This was taken
care for some other attributes of the Port resource like allowed
address pairs, but not all.
Even though the API is lax about the order of specific attributes, we
should attempt to restore the old behavior to avoid more damaging side
effects in clients that are assuming the list be returned in the order
in which fixed IPs are created.
[1] https://review.openstack.org/#/c/373582
[2] https://www.google.com/url?q=http%3A%2F%2Flogs.openstack.org%2F63%2F377163%2F4%2Fcheck%2Fgate-shade-dsvm-functional-neutron%2Fe621e3d%2Fconsole.html&sa=D&sntz=1&usg=AFQjCNG3xbH0QxdjxrkuAseWtPGpUm4heg
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1630410/+subscriptions
Follow ups