[RabbitMQ] need to deprecate commands "service rabbitmq-server stop" and "service rabbitmq-server start"
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Mirantis OpenStack | Status tracked in 10.0.x | |||||
10.0.x |
Confirmed
|
Medium
|
MOS Oslo | |||
8.0.x |
Won't Fix
|
Medium
|
MOS Oslo | |||
9.x |
Confirmed
|
Medium
|
MOS Oslo |
Bug Description
We need to deprecate commands "service rabbitmq-server stop" and "service rabbitmq-server start" because these commands don't work and broke RabbitMQ cluster. We need to use pacemaker instead and restart Rabbit MQ services with the following commands:
pcs resource disable p_rabbitmq-server
pcs resource enable p_rabbitmq-server
Steps To Reproduce:
1) Restart RabbitMQ using "service" command:
service rabbitmq-server stop
service rabbitmq-server start
2) Check RabbitMQ status in pacemaker.
Actual Result:
RabbitMQ cluster brocken and pacemaker can't start RabbitMQ on this node, because 'service rabbitmq-server start' will remove and change pid of the process.
Expected Result:
Commands 'service rabbitmq-server start' and 'service rabbitmq-server stop' are not available of controllers and it is possible to restart RabbitMQ only with pacemaker.
The issue reproduced on 7.0, 8.0 and 9.0 versions.
Changed in mos: | |
importance: | Undecided → Medium |
assignee: | nobody → Dmitry Mescheryakov (dmitrymex) |
Changed in mos: | |
milestone: | 8.0 → none |
assignee: | Dmitry Mescheryakov (dmitrymex) → nobody |
importance: | Medium → Undecided |
Changed in mos: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
assignee: | nobody → Dmitry Mescheryakov (dmitrymex) |
milestone: | none → 9.0 |
assignee: | Dmitry Mescheryakov (dmitrymex) → MOS Oslo (mos-oslo) |
description: | updated |
tags: | removed: need-info |
Changed in mos: | |
status: | Confirmed → Won't Fix |
Changed in mos: | |
status: | Won't Fix → Confirmed |
milestone: | 9.0 → 9.1 |
tags: | added: 10.0-reviewed |
Hmm, how are we going to 'deprecate' those?
Should we just avoid using those commands?