root@greene:/home/duncan# pcs cluster setup --name pacemaker1 pinke greene
greene: Authorized
pinke: Authorizedroot@greene:/home/duncan#root@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@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.
Thanks
Duncan Hare
714 931 7952
From: Valentin Vidic <[email protected]>
To: Duncan Hare <[email protected]>
Cc: [email protected]
Sent: Thursday, October 25, 2018 9:44 AM
Subject: Re: [Debian-ha-maintainers] Bug#911801: pacemaker: Cannot complete
pcs cluster setup command, returns error HTTP401
On Wed, Oct 24, 2018 at 05:19:02PM -0700, Duncan Hare wrote:
> Package: pacemaker
> Version: 1.1.16-1
> Severity: grave
> Justification: causes non-serious data loss
I've reassigned this to pcs package, since it probably doesn't have to
do with pacemaker, but I'm not sure what is going on here. Can you
provide some more info on the problem and pcs commands that where used
so I can try to reproduce?
Also, perhaps the README.Debian included in the pcs package could help
if this is an initial installation of the cluster.
--
Valentin
