pcmk_remote is not ordered after wait-for-settle on rhel8
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
puppet-pacemaker |
Fix Released
|
Undecided
|
Michele Baldessari |
Bug Description
We currently have the following ordering constraints collectors:
Exec<| title == 'wait-for-settle' |> -> Pcmk_constraint<||>
Exec<| title == 'wait-for-settle' |> -> Pcmk_resource<||>
Exec<| title == 'wait-for-settle' |> -> Pcmk_property<||>
Exec<| title == 'wait-for-settle' |> -> Pcmk_bundle<||>
The problem here is that on rhel8 remotes are a dedicated puppet resource 'pcmk_remote'. From manifests/
if $::pacemaker:
pcmk_remote { $name:
ensure => $ensure,
...
} else {
pcmk_resource { $name:
ensure => $ensure,
This means that on rhel8 we do not have the guarantee that remotes will be created after the cluster has settled. This has been observed in a real-life scenario (the wait-for-settle took place *after* the error):
Mar 12 01:51:05 controller-
Changed in puppet-pacemaker: | |
assignee: | nobody → Michele Baldessari (michele) |
Fix proposed to branch: master /review. opendev. org/712623
Review: https:/