fence_scsi device parameter update (addition/deletion) causes restart of all resources
Issue
- Does it possible to create an independent fence_scsi device for every new resource group that is supposed to add/remove in future?
- Each time an update on the fence_scsi device parameter causes a restart of all resources.
- Do we have any other options in the fence_scsi configuration that can be used to avoid cluster-wide resource restart after updating fence_scsi configuration?
node2 pengine: info: rsc_action_digest_cmp: Parameters to ig-scsi-fnc_start_0 on node1 changed: was 5c6b7753cebc986370b0b74dd3e45abb vs. now 6f915787eee272807dae881764428afd (reload:3.0.14) 0:0;4:3:0:3de2b23c-09d6-4f7c-8709-5ceae047e66f
node2 pengine: notice: LogNodeActions: * Fence (on) node1 'Device parameters changed (reload)'
node2 pengine: notice: LogAction: * Restart ig-scsi-fnc ( node1 ) due to resource definition change
node2 pengine: notice: LogAction: * Restart db1_igt_lvm ( node1 ) due to required stonith
node2 pengine: notice: LogAction: * Restart bck_igt_lvm ( node1 ) due to required stonith
node2 pengine: notice: LogAction: * Restart db2_igt_lvm ( node1 ) due to required stonith
node2 pengine: notice: LogAction: * Restart db1_igt_fs ( node1 ) due to required stonith
node2 pengine: notice: LogAction: * Restart online_igt_fs ( node1 ) due to required stonith
node2 pengine: notice: LogAction: * Restart exp_igt_fs ( node1 ) due to required stonith
node2 pengine: notice: LogAction: * Restart db2_igt_fs ( node1 ) due to required stonith
node2 pengine: notice: LogAction: * Restart ora_igt_vip ( node1 ) due to required stonith
node2 pengine: notice: LogAction: * Restart ora_igt_ap ( node1 ) due to required stonith
Environment
- Red Hat Enterprise Linux (RHEL) 7, 8 with the High Availability Add-On
- fence_scsi
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.