AgentListener doesn't respect per-region RabbitMQs
Bug #1602404 reported by
Stan Lagun
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Murano |
Fix Released
|
Medium
|
Stan Lagun | ||
| Mitaka |
New
|
Medium
|
Stan Lagun | ||
| Newton |
Fix Released
|
Medium
|
Stan Lagun | ||
Bug Description
In multi-region setups each OpenStack region might have a dedicated RabbitMQ server form Agent <-> Engine communications. Agent interface to MuranoPL respects ability to have separate RabbitMQ configuration per region. But the same is not true for the AgentListener which is waits for agent responses. As a result results of command execution will never reach the engine. This only takes place when ability to deploy apps into regions other than the home is used (experimental feature)
| Changed in murano: | |
| importance: | Undecided → Medium |
| assignee: | nobody → Stan Lagun (slagun) |
| milestone: | none → newton-2 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to murano (master) | #1 |
| Changed in murano: | |
| status: | New → In Progress |
| Changed in murano: | |
| milestone: | newton-2 → newton-3 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to murano (master) | #2 |
| Changed in murano: | |
| status: | In Progress → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/murano 3.0.0.0b3 | #3 |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/