rpc-related parameters for OS components need to be verified
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Alexey Deryugin | ||
Mitaka |
Won't Fix
|
High
|
Unassigned |
Bug Description
Detailed bug description:
Recently nearly all puppet-openstack modules were refactored to use common oslo::messaging
https:/
Steps to reproduce:
Deploy recent MOS 10.0 ISO
Expected results:
All rpc-related parameters are set to the same values as it was before modules refactoring (as in MOS 9.0, for example)
Actual result:
rpc-related parameters are set to default values which are not always expected
Changed in fuel: | |
importance: | Undecided → High |
assignee: | nobody → MOS Puppet Team (mos-puppet) |
milestone: | none → 10.0 |
status: | New → Confirmed |
Changed in fuel: | |
status: | Confirmed → In Progress |
Changed in fuel: | |
status: | Fix Committed → In Progress |
Changed in fuel: | |
assignee: | MOS Puppet Team (mos-puppet) → Alexey Deryugin (velovec) |
Changed in fuel: | |
assignee: | Alexey Deryugin (velovec) → Alex Schultz (alex-schultz) |
Changed in fuel: | |
assignee: | Alex Schultz (alex-schultz) → Alexey Deryugin (velovec) |
tags: | added: 9.1-opposed |
Puppet "heat" module doesn't have defaults changings.
Puppet "keystone" module has only one change in defaults - "rabbit_ha_queues", but this parameter is properly handled in "oslo" module (so behavior is not changed).
These modules shouldn't have such problems.