If we run cluster task on one controller and pacemaker isn't alive (dead or not fully up yet) on other 2 controller, the cluster tasks hangs on:
/usr/sbin/crm_attribute -q --type crm_config --query --name dc-version
If pacemaker service become up on other nodes, the cluster task still hangs on this command. The issue I see here that cibadmin query isn't refreshed before `/usr/sbin/crm_attribute -q --type crm_config --query --name dc-version` command. That's why I think we need to update it every time.
If we run cluster task on one controller and pacemaker isn't alive (dead or not fully up yet) on other 2 controller, the cluster tasks hangs on: crm_attribute -q --type crm_config --query --name dc-version
/usr/sbin/
If pacemaker service become up on other nodes, the cluster task still hangs on this command. The issue I see here that cibadmin query isn't refreshed before `/usr/sbin/ crm_attribute -q --type crm_config --query --name dc-version` command. That's why I think we need to update it every time.
https:/ /review. fuel-infra. org/#/c/ 25620/ -fix for puppet-pacemaker module.