reconnect_interval got broken with the pcs 0.10 migration
Bug #1905606 reported by
Michele Baldessari
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| puppet-pacemaker |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
When switching to the pcs 0.10 providers we moved from the the general pcmk_resource provider to the pcmk_remote backend. While doing this we lost the ability to specify the reconnect_interval.
Revision history for this message
| Michele Baldessari (michele) wrote | #1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/puppet-pacemaker 1.2.0 | #2 |
| Changed in puppet-pacemaker: | |
| status: | New → Fix Released |
To post a comment you must log in.
https:/