[Debian-ha-maintainers] Bug#911801: Bug#911801: pacemaker: Cannot complete pcs cluster setup command, returns error HTTP401

[Valentin Vidic]

On Thu, Oct 25, 2018 at 05:11:17PM +0000, Duncan Hare wrote:
> root at greene:/home/duncan# pcs cluster setup --name pacemaker1 pinke greene
> greene: Authorized
> pinke: Authorizedroot at greene:/home/duncan#root at greene:/home/duncan# pcs cluster setup --name pacemaker1 pinke greene --force
> Destroying cluster on nodes: pinke, greene...
> pinke: Unable to authenticate to pinke - (HTTP error: 401), try running 'pcs cluster auth'
> greene: Unable to authenticate to greene - (HTTP error: 401), try running 'pcs cluster auth'
> pinke: Unable to authenticate to pinke - (HTTP error: 401), try running 'pcs cluster auth'
> greene: Unable to authenticate to greene - (HTTP error: 401), try running 'pcs cluster auth'
> Error: unable to destroy cluster
> greene: Unable to authenticate to greene - (HTTP error: 401), try running 'pcs cluster auth'
> pinke: Unable to authenticate to pinke - (HTTP error: 401), try running 'pcs cluster auth'
> root at greene:/home/duncan#
> 
> this works: rm /etc/corosync/corosync.conf
> 
> Debian Bug report logs - #847295
> pcs cluster setup does not overwrite existing config files, and the n the cluster create fails.

Yes, I think removing corosync.conf is documented in README.Debian:

As PCS expects Corosync and Pacemaker to be in unconfigured state,
the following command needs to be executed on all cluster nodes to
stop the services and delete their default configuration:

  # pcs cluster destroy
  Shutting down pacemaker/corosync services...
  Killing any remaining services...
  Removing all cluster configuration files...

-- 
Valentin