AgentListener doesn't stop after GC cleanup
Bug #1449500 reported by
Stan Lagun
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Murano |
Fix Released
|
Critical
|
Stan Lagun | ||
Kilo |
Fix Released
|
Critical
|
Stan Lagun | ||
Liberty |
Fix Released
|
Critical
|
Stan Lagun |
Bug Description
Any application/class may have "destroy" method that is being called during garbage collection. If such method needs to send execution plan to murano-agent (for example to uninstall something) AgentListener will be started and results queue in RabbitMQ will be consumed. After GC phase there is a deployment phase and it typically requires to also send execution plans. Because GC runs on ObjectCopy and deployment on Objects 2 different instances if AgentListener will be created consuming the same queue and stealing messages from each other.
Changed in murano: | |
status: | New → Confirmed |
Changed in murano: | |
milestone: | none → kilo-rc2 |
Changed in murano: | |
status: | Fix Committed → Fix Released |
Changed in murano: | |
milestone: | kilo-rc2 → 2015.1.0 |
tags: | added: juno-backport-potential |
Changed in murano: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fix proposed to branch: stable/kilo /review. openstack. org/178717
Review: https:/