tripleo

  1. Bug #1750880
  2. Comment #1

Comment 1 for bug 1750880

Revision history for this message
Michele Baldessari (michele) wrote : Re: [queen promotion] fs035 is failing to deploy the overcloud - pacemaker is not starting

So the failure is due to the pcsd service not starting because it times out:
Feb 21 16:26:14 overcloud-controller-0 systemd[1]: Starting PCS GUI and remote configuration interface...
Feb 21 16:27:44 overcloud-controller-0 systemd[1]: pcsd.service start operation timed out. Terminating.
Feb 21 16:28:07 overcloud-controller-0 systemd[1]: Failed to start PCS GUI and remote configuration interface.
Feb 21 16:28:07 overcloud-controller-0 systemd[1]: Unit pcsd.service entered failed state.
Feb 21 16:28:07 overcloud-controller-0 systemd[1]: pcsd.service failed.
Error: /Stage[main]/Pacemaker::Service/Service[pcsd]/ensure: change from stopped to running failed: Systemd start for pcsd failed!

The only time I have seen this happening is when pcsd could not resolve DNS properly, the queries it did would slow the startup down and eventually it timed out. Not sure this is the case here yet, though. We do not seem to collect /var/log/pcsd any longer?

Is this a reproduceable failure?