OCF: Use private attributes to not trigger pacemaker transitions on each update
Bug #1524672 reported by
Bogdan Dobrelya
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
Medium
|
Liubov Efremova | ||
Mitaka |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
According to Andrew's comments https:/
That means that "crm_attribute -N <node>" should be replaced to private attributes with "attrd_updater", see examples
https:/
https:/
Note, for some cases other nodes should be able to see attributes of each other. For such cases, private attributes should not be used.
description: | updated |
description: | updated |
summary: |
- OCF: Use private attributes to not trigger peacemaker transitions on - each update + OCF: Use private attributes to not trigger pacemaker transitions on each + update |
Changed in fuel: | |
status: | New → Confirmed |
tags: | added: team-bugfix |
Changed in fuel: | |
milestone: | 8.0 → 9.0 |
Changed in fuel: | |
assignee: | Fuel Library Team (fuel-library) → Liubov Efremova (lefremova) |
tags: | added: keep-in-9.0 |
Changed in fuel: | |
assignee: | Liubov Efremova (lefremova) → MOS Linux (mos-linux) |
Changed in fuel: | |
assignee: | MOS Linux (mos-linux) → Ivan Suzdal (isuzdal) |
To post a comment you must log in.
I'm not sure of the impact of this issue. Is it so bad to have extra transitions? Maybe not, but still it'd be better not having them for sure. That is why I put the medium prio