Deployment failing: task rabbitmq timeout on secondary controllers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Ivan Suzdal | ||
Newton |
Fix Released
|
High
|
Ivan Suzdal | ||
Ocata |
Fix Committed
|
High
|
Ivan Suzdal |
Bug Description
The task rabbitmq/
The ocf resource is created, but doesn't seem to start manually either. Task rabbitmq fails and deployment is stopped on all nodes other than the secondary controllers which move into error state.
Steps to reproduce:
- Create environment
- Add 3 controllers and any other set of nodes
- Deploy environment
Expected results:
- rabbitmq-server is added as an ocf resource to the pacemaker cluster and environment is deployed
Actual results:
- rabbitmq-server ocf resources are created, but do not start on any secondary controllers
Reproducibility:
- This is happening on all environments I'm deploying with any version of fuel 10+
Impact:
- Unable to deploy any environment
Description of the environment:
- Fuel 10.0
- Newton on Ubuntu 16.04
- KVM
- Neutron with tunneling segmentation
- Ceph for all storage types
Changed in fuel: | |
status: | Incomplete → New |
Changed in fuel: | |
assignee: | Fuel for Openstack (fuel) → MOS Oslo (mos-oslo) |
milestone: | 10.x-updates → 10.1 |
Please attach diagnostic snapshot, marking as Incomplete.