RabbitMQ OCF applications check should rely on the 'kernel' module running instead of exit code
Bug #1446251 reported by
Bogdan Dobrelya
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
Critical
|
Alexander Nevenchannyy | ||
5.1.x |
Fix Committed
|
Critical
|
Bogdan Dobrelya | ||
6.0.x |
Fix Committed
|
Critical
|
Bogdan Dobrelya |
Bug Description
This issue was discovered at the scale lab, when rabbit nodes were running under load.
In the get_status() https:/
Current logic relies on the exit code only. But it should check at least the 'kernel' module running, otherwise report "not running".
These issues may appear only when the specified timeout for commands to stop or wait have exceeded. That is a usual case under load, hence is critical by its impact.
Changed in fuel: | |
milestone: | none → 6.1 |
status: | New → In Progress |
assignee: | nobody → Bogdan Dobrelya (bogdando) |
importance: | Undecided → Critical |
tags: | added: scale |
Changed in fuel: | |
assignee: | Bogdan Dobrelya (bogdando) → Alexander Nevenchannyy (anevenchannyy) |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/175457
Review: https:/