DescriptionLars Kellogg-Stedman
2018-11-07 14:59:57 UTC
We have successfully deployed an OSP 13 overcloud, but the fencing configuration was incorrect. Specifically, the fencing configuration had the wrong hostnames in pcmk_host_list for each device. We have:
Resource: stonith-fence_ipmilan-000f530df538 (class=stonith type=fence_ipmilan)
Attributes: ipaddr=10.0.15.39 lanplus=true login=root passwd=***** pcmk_host_list=overcloud-controller-0 privlvl=administrator
But we want pcmk_host_list to use real hostnames (such as
neu-3-39-control3). I've updated the fencing configuration and
redeployed, and while the stack environment has the desired
configuration:
$ openstack stack environment show overcloud
[...]
FencingConfig:
devices:
- agent: fence_ipmilan
host_mac: 00:0f:53:0d:fa:60
params:
ipaddr: 10.0.3.39
lanplus: true
login: root
passwd: ******
pcmk_host_list: neu-3-39-control3
privlvl: administrator
[...]
The fencing configuration in pacemaker retains the incorrect values:
[root@neu-3-39-control3 ~]# pcs stonith show --full
Resource: stonith-fence_ipmilan-000f530df538 (class=stonith type=fence_ipmilan)
Attributes: ipaddr=10.0.15.39 lanplus=true login=root passwd=***** pcmk_host_list=overcloud-controller-0 privlvl=administrator
Operations: monitor interval=60s (stonith-fence_ipmilan-000f530df538-monitor-interval-60s)
Resource: stonith-fence_ipmilan-000f530dfa60 (class=stonith type=fence_ipmilan)
Attributes: ipaddr=10.0.3.39 lanplus=true login=root passwd=***** pcmk_host_list=overcloud-controller-2 privlvl=administrator
Operations: monitor interval=60s (stonith-fence_ipmilan-000f530dfa60-monitor-interval-60s)
Resource: stonith-fence_ipmilan-000f53281af0 (class=stonith type=fence_ipmilan)
Attributes: ipaddr=10.0.5.39 lanplus=true login=root passwd=***** pcmk_host_list=overcloud-controller-1 privlvl=administrator
Operations: monitor interval=60s (stonith-fence_ipmilan-000f53281af0-monitor-interval-60s)
What is the appropriate mechanism for updating these values?
Comment 1Lars Kellogg-Stedman
2018-11-07 15:18:08 UTC
(I was able to update this by hand by running the appropriate sequence of 'pcs stonith update ...' commands. I'm interested in whether there is a way to have this happen as part of the stack update.)
puppet-pacemaker has traditionally been satisfied with "the object exists" and not checked for any changes.
This is a known problem that we're actively working towards fixing, but is unlikely to be back ported.
Comment 3Michele Baldessari
2019-05-08 09:31:19 UTC
*** Bug 1693422 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2020:0643
We have successfully deployed an OSP 13 overcloud, but the fencing configuration was incorrect. Specifically, the fencing configuration had the wrong hostnames in pcmk_host_list for each device. We have: Resource: stonith-fence_ipmilan-000f530df538 (class=stonith type=fence_ipmilan) Attributes: ipaddr=10.0.15.39 lanplus=true login=root passwd=***** pcmk_host_list=overcloud-controller-0 privlvl=administrator But we want pcmk_host_list to use real hostnames (such as neu-3-39-control3). I've updated the fencing configuration and redeployed, and while the stack environment has the desired configuration: $ openstack stack environment show overcloud [...] FencingConfig: devices: - agent: fence_ipmilan host_mac: 00:0f:53:0d:fa:60 params: ipaddr: 10.0.3.39 lanplus: true login: root passwd: ****** pcmk_host_list: neu-3-39-control3 privlvl: administrator [...] The fencing configuration in pacemaker retains the incorrect values: [root@neu-3-39-control3 ~]# pcs stonith show --full Resource: stonith-fence_ipmilan-000f530df538 (class=stonith type=fence_ipmilan) Attributes: ipaddr=10.0.15.39 lanplus=true login=root passwd=***** pcmk_host_list=overcloud-controller-0 privlvl=administrator Operations: monitor interval=60s (stonith-fence_ipmilan-000f530df538-monitor-interval-60s) Resource: stonith-fence_ipmilan-000f530dfa60 (class=stonith type=fence_ipmilan) Attributes: ipaddr=10.0.3.39 lanplus=true login=root passwd=***** pcmk_host_list=overcloud-controller-2 privlvl=administrator Operations: monitor interval=60s (stonith-fence_ipmilan-000f530dfa60-monitor-interval-60s) Resource: stonith-fence_ipmilan-000f53281af0 (class=stonith type=fence_ipmilan) Attributes: ipaddr=10.0.5.39 lanplus=true login=root passwd=***** pcmk_host_list=overcloud-controller-1 privlvl=administrator Operations: monitor interval=60s (stonith-fence_ipmilan-000f53281af0-monitor-interval-60s) What is the appropriate mechanism for updating these values?