Updating overcloud fails when adding storage, and then pcs commands show "free(): invalid next size (normal)" message.

Diagnostic Steps

• When an administrator tried to add some storage into the cluster, it failed as below.

  $ openstack overcloud deploy ...(options) 
  ...
  xxx xx xx:xx:xx puppet-user: error: Could not connect to controller: Transport endpoint is not connected
  xxx xx xx:xx:xx puppet-user: Error: /Stage[main]/Tripleo::Fencing/Pacemaker::Stonith::Level[stonith-1-xxxx]/Pcmk_stonith_level[stonith-level-1-$(/usr/sbin/crm_node -n)-stonith-fence_kdump-xxxxxxxxxxxx_stonith-fence_compute-fence-nova]: Could not evaluate: pcs -f  stonith level | sed -n \"/^Target: $(/usr/sbin/crm_node -n)$/,/^Target:/{/^Target: $(/usr/sbin/crm_node -n)$/b;/^Target:/b;p}\" | grep -e \"Level[[:space:]]*1[[:space:]]*-[[:space:]]
  *stonith-fence_kdump-xxxx,stonith-fence_compute-fence-nova\" failed: . Too many tries\n
  xxx xx xx:xx:xx puppet-user: Error: /Stage[main]/Tripleo::Fencing/Pacemaker::Stonith::Level[stonith-2-xxxx]/Pcmk_stonith_level[stonith-level-2-$(/usr/sbin/crm_node -n)-stonith-fence_ipmilan-xxxx_stonith-fence_compute-fence-nova]: Could not evaluate: pcs -f  stonith level | sed -n \"/^Target: $(/usr/sbin/crm_node -n)
  ...
  [2023-xx-xx xx:xx:xx.xxx] 2023-xx-xx xx:xx:xx.xxx | xxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx |      FATAL | Wait for puppet host configuration to finish | $HOSTNAME | error={"ansible_job_id": "xxxxx.xxxxx", "attempts": 360, "changed": false, "failed_when_result": true, "finished": 0, "started": 1}
  

• When they executed the pcs command, "Error: error running crm_mon, is pacemaker running?" was displayed..

  $ sudo pcs status --full
  Error: error running crm_mon, is pacemaker running?
  free(): invalid next size (normal)
  

• Confirming a core dump, it was aborted due to a buffer overflow consumed by storage mapping data.

  #1  0x0000ZZZZZZZZZZZZ in __GI_abort () at abort.c:79
  #2  0x0000ZZZZZZZZZZZZ in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0xAAAAAAAAAAAA "%s\n") at ../sysdeps/posix/libc_fatal.c:181
  #3  0x0000ZZZZZZZZZZZZ in malloc_printerr (str=str@entry=0xBBBBBBBBBBBB "free(): invalid next size (normal)") at malloc.c:5374
  #4  0x0000ZZZZZZZZZZZZ in _int_free (av=0xCCCCCCCCCCCC <main_arena>, p=0xDDDDDDDDDDDD, have_lock=<optimized out>) at malloc.c:4334
  
  (gdb) x/64s 0xDDDDDDDDDDDD
  ...
  0xZZZZZZZZZZZZ: " -e PCMK_stderr=1 --net=host -e PCMK_remote_port=3121 -v /etc/hosts:/etc/hosts:ro -v /etc/localtime:/etc/localtime:ro -v /etc/pki/ca-trust/extracted:/etc/pki/ca-trust/extracted:ro -v /etc/pki/ca-trust"...
  0xZZZZZZZZZZZZ: "/source/anchors:/etc/pki/ca-trust/source/anchors:ro -v /etc/pki/tls/certs/ca-bundle.crt:/etc/pki/tls/certs/ca-bundle.crt:ro -v /etc/pki/tls/certs/ca-bundle.trust.crt:/etc/pki/tls/certs/ca-bundle.trust"...
  0xZZZZZZZZZZZZ: ".crt:ro -v /etc/pki/tls/cert.pem:/etc/pki/tls/cert.pem:ro -v /dev/log:/dev/log:rw -v /etc/puppet:/etc/puppet:ro -v /var/lib/config-data/puppet-generated/cinder:/var/lib/kolla/config_files/src:ro -v /v"...
  ...
  ...             (Long arguments related to storage mapping points were seen here.)
  ...
  0xZZZZZZZZZZZZ: "/kolla/config_files/cinder_volume.json:/var/lib/kolla/config_files/config.json:ro -v /etc/iscsi:/var/lib/kolla/config_files/src-iscsid:ro -v /etc/ceph:/var/lib/kolla/config_files/src-ceph:ro -v /lib/m"...
  0xZZZZZZZZZZZZ: "odules:/lib/modules:ro -v /dev/:/dev/:rw -v /run/:/run/:rw -v /sys:/sys:rw -v /var/lib/cinder:/" 
  0xZZZZZZZZZZZZ: ""