RabbitMQ OCF action stop would fail if there is no pid file exist
Bug #1446526 reported by
Bogdan Dobrelya
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Bogdan Dobrelya | ||
5.1.x |
Won't Fix
|
High
|
Denis Meltsaykin | ||
6.0.x |
Won't Fix
|
High
|
Denis Meltsaykin |
Bug Description
Currently, the action stop would fail if there is no pid file exist for some reason, but rabbit beam process might still be running.
stop_server_
how to reproduce:
1) rm -f /var/run/
2) ocf_handler_
As a solution, it should instead invoke 'rabbitmqctl stop' and return generic error only if this operation have failed as well. Note, it should not try to find beam process in ps and kill it as this could affect other rabbitmq instances running around.
description: | updated |
Changed in fuel: | |
milestone: | none → 6.1 |
importance: | Undecided → High |
assignee: | nobody → Bogdan Dobrelya (bogdando) |
status: | New → In Progress |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/175785
Review: https:/