RabbitMQ OCF node uptime is not always reset in the CIB
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Bogdan Dobrelya | ||
7.0.x |
Confirmed
|
High
|
Denis Puchkin | ||
8.0.x |
Fix Released
|
High
|
Bogdan Dobrelya | ||
Mitaka |
Fix Released
|
High
|
Bogdan Dobrelya |
Bug Description
Source bug https:/
What I found is that the uptime value was not reset for the node-3 after it was rebooted, which is wrong and impacts election of new masters very badly:
node-4 lrmd:
before node-3 reset
2015-12-
2015-12-
after node-3 reset
2015-12-
2015-12-
The crm_mon -fotAW -1 also shows the value for the node's rabbit-start-time is not being reset after the non-graceful shutdown.
Changed in fuel: | |
importance: | Undecided → High |
milestone: | none → 8.0 |
assignee: | nobody → Bogdan Dobrelya (bogdando) |
status: | New → In Progress |
tags: | added: area-build |
tags: |
added: area-library ha rabbitmq removed: area-build |
summary: |
- RabbitMQ OCF node uptime is not reset in the CIB + RabbitMQ OCF node uptime is not always reset in the CIB |
tags: | added: team-bugfix |
tags: | added: on-verification |
tags: | added: on-verification |
Fix proposed to branch: master /review. openstack. org/262572
Review: https:/