pacemaker deploy fails with 401 while trying to setup cluster

Bug #1639972 reported by Alex Schultz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
High
Unassigned

Bug Description

While trying to run a basic HA deploy following the documentation on tripleo.org, the deployment is failing with an error 6. It appears that it's not running the commands to properly configure auth when dealing with the pacemaker setup.

http://paste.openstack.org/show/588324/

Deployment command:
openstack overcloud deploy --libvirt-type=qemu -t 80 --control-scale 3 --ntp-server 0.centos.pool.ntp.org -e /usr/share/openstack-tripleo-heat-templates/environments/puppet-pacemaker.yaml --templates /usr/share/openstack-tripleo-heat-templates/

description: updated
Changed in tripleo:
status: New → Confirmed
importance: Undecided → High
milestone: none → ocata-1
Revision history for this message
Michele Baldessari (michele) wrote :

Hi Alex,

this one concerns me quite a bit as I have never seen this before. Can we try to enable puppet debug and see exactly which pcs sequence is being called? Is this master/newton or something else?

thanks,
Michele

Revision history for this message
Alex Schultz (alex-schultz) wrote :

It's master, I've actually never been able to get this working. I'm deploying on an ovb environment with the above command. I'll try and grab some logs today.

Revision history for this message
Alex Schultz (alex-schultz) wrote :

Here's the puppet logs from a failed environment. I'm working on getting a run with puppet debug enabled.

Revision history for this message
Alex Schultz (alex-schultz) wrote :

Here's the debug version of the puppet logs

Steven Hardy (shardy)
Changed in tripleo:
milestone: ocata-1 → ocata-2
Changed in tripleo:
milestone: ocata-2 → ocata-3
Changed in tripleo:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.