Hide Forgot
Description of problem: It seems the overcloud deployment fails during the pacemaker deployment with 02:36:30.711 \u001b[1;31mError: /usr/sbin/pcs cluster auth overcloud-controller-0 overcloud-controller-1 overcloud-controller-2 -u hacluster -p znhwdgiBub0FthZt --force returned 1 instead of one of [0]\u001b[0m 02:36:30.711 \u001b[1;31mError: /Stage[main]/Pacemaker::Corosync/Exec[auth-successful-across-all-nodes]/returns: change from notrun to 0 failed: /usr/sbin/pcs cluster auth overcloud-controller-0 overcloud-controller-1 overcloud-controller-2 -u hacluster -p znhwdgiBub0FthZt --force returned 1 instead of one of [0]\u001b[0m 02:36:30.711 \u001b[1;31mWarning: /Stage[main]/Pacemaker::Corosync/Exec[wait-for-settle]: Skipping because of failed dependencies\u001b[0m 02:36:30.711 \u001b[1;31mWarning: /Stage[main]/Pacemaker::Corosync/Notify[pacemaker settled]: Skipping because of failed dependencies\u001b[0m 02:36:30.711 \u001b[1;31mWarning: /Stage[main]/Pacemaker::Stonith/Exec[Disable STONITH]: Skipping because of failed dependencies\u001b[0m Version-Release number of selected component (if applicable): core puddle: 2016-03-17.1 director puddle: 2016-03-09.1 How reproducible: 100% Steps to Reproduce: 1. Deploy with IPv6 in a HA controllers using the puddles listed (latest ones when the bug was filed).
This turned out to be a downstream testing issue due to not including "environments/net-single-nic-with-vlans-v6.yaml" in the deployment command. Thus the overcloud nodes didn't have the IPv6 addresses properly set up. Closing bug.