AgentListener doesn't stop after GC cleanup
Bug #1449645 reported by
Victor Ryzhenkin
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
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.
The same bug in upstream: https:/
Changed in mos: | |
milestone: | none → 6.1 |
Changed in mos: | |
status: | Confirmed → In Progress |
Changed in mos: | |
status: | In Progress → Won't Fix |
status: | Won't Fix → Fix Committed |
Changed in mos: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fix proposed to branch: openstack- ci/fuel- 6.1/2014. 2 /review. fuel-infra. org/6376
Change author: Stan Lagun <email address hidden>
Review: https:/