MySQL OCF RA stop is not reliable
Bug #1585125 reported by
Bogdan Dobrelya
This bug report is a duplicate of:
Bug #1583173: MySQL OCF RA action monitor must check if a seed node is running the most recent of known GTIDs.
Edit
Remove
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Bogdan Dobrelya | ||
6.1.x |
Triaged
|
High
|
MOS Maintenance | ||
7.0.x |
Fix Committed
|
High
|
MOS Maintenance | ||
8.0.x |
Fix Committed
|
High
|
Anton Chevychalov | ||
Mitaka |
Fix Released
|
High
|
Bogdan Dobrelya | ||
Newton |
Fix Released
|
High
|
Bogdan Dobrelya |
Bug Description
If there is an SST in progress or stalled, the action stop will report successfully stopped as there is no pid found. But it shall check for SST as well. And if found, call the proc_stop. Only this way we can be sure the process has been stopped.
UX is high as it may leave a stale mysqld running and render the resource instance lost for a control plane, for example waiting for an SST to finish, which will never to happen.
Changed in fuel: | |
importance: | Undecided → High |
assignee: | nobody → Bogdan Dobrelya (bogdando) |
milestone: | none → 10.0 |
tags: | added: galera |
tags: | added: area-library |
tags: | added: on-verification |
To post a comment you must log in.
Change abandoned by Bogdan Dobrelya (<email address hidden>) on branch: master /review. openstack. org/287733
Review: https:/