Floating IP creation causes multiple notifications
Bug #1561638 reported by
Thomas Bachman
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Group Based Policy |
Fix Released
|
Medium
|
Thomas Bachman |
Bug Description
Creation of a floating IP causes duplicate notifications to the agents. This is not harmful, but is also not necessary.
Changed in group-based-policy: | |
milestone: | none → next |
assignee: | nobody → Thomas Bachman (bachman) |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in group-based-policy: | |
status: | Confirmed → In Progress |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/297307 /git.openstack. org/cgit/ openstack/ group-based- policy/ commit/ ?id=256eac720f6 a81777d576607af 689b9ec216af6f
Committed: https:/
Submitter: Jenkins
Branch: master
commit 256eac720f6a817 77d576607af689b 9ec216af6f
Author: Thomas Bachman <email address hidden>
Date: Tue Mar 22 18:45:56 2016 -0400
Refactor for create_floatingip call
The current implementation for create_floatingip results in the
L3 API being called twice. The first pass causes additional attributes
to be populated, which are used in the second call. This patch converts
this to a single call, which gets the parameters needed and continues,
rather than call itself recursively.
Change-Id: Ie9a3a57d2186fd 693e9bc1e03501f 0038e316b41
Closes-Bug: #1561638