loadbalancer id is omittted from listener events, causing caching issues
Bug #1509595 reported by
Adam Gandelman
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Astara |
Fix Released
|
High
|
Adam Gandelman | ||
Liberty |
Fix Committed
|
High
|
Adam Gandelman |
Bug Description
when the loadbalancer processes a listener.create event, it misses the loadbalancer id, causing the worker to consult the tenant resource cache for the loadbalancer. if the tenant previously had a loadbalancer that was deleted, the cache ends up returning that and the SM passes on it since its wrong/deleted. we can fix this by ensuring the lb id is extracted from listener events correctly.
to reproduce: create a loadbalancer, then a listener. delete them, create another. the balancer will be created but subsequent listener updates will be dropped, as the rug thinks they are intended for the first deleted balancer.
Changed in astara: | |
importance: | Undecided → High |
assignee: | nobody → Adam Gandelman (gandelman-a) |
Changed in astara: | |
milestone: | none → mitaka-1 |
Changed in astara: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/239145 /git.openstack. org/cgit/ openstack/ astara/ commit/ ?id=0f05f08fda5 d3c5b4e44fb43b5 496b5bda1dd00b
Committed: https:/
Submitter: Jenkins
Branch: master
commit 0f05f08fda5d3c5 b4e44fb43b5496b 5bda1dd00b
Author: Adam Gandelman <email address hidden>
Date: Fri Oct 23 20:50:37 2015 -0700
Extract loadbalancer_id from listener create events
We're currently dropping the lb id from listener events, causing
a cache lookup that ends up hitting deleted loadbalancers instead
of the intended one. This fixes it and looks for loadbalancer_id
in the correct place of listener create events body.
Change-Id: Ic94a8ecbd227d0 97b25ea004cc8bd 7ac76c40580
Closes-bug: #1509595