Just want to say "Thank you!" to the OP: Jonathan Meisel
This still not fixed in latest Debian release. I was bang my head against a
wall until I found this tread.
The initial bug report is still true for my Debian:
root@ivr02:~# lsb_release -rd
Description:Debian GNU/Linux 9.1 (stretch)
** Changed in: pcs (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640923
Title:
pcs cluster auth does not generate "tokens" file
To manage notifications
I do agree that, since PCS can manage an existing installed cluster - I
haven't considered this for all my previous posts/comments/patches - PCS
installation should NOT try to take care of corosync/pacemaker files.
Whoever is dealing with PCS has to handle it properly AFTER
installation. Argument
Upstream discussion followed here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847294
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847295
And last statement is this (from Maintainer):
> On Thu, Dec 08, 2016 at 06:27:48PM -0200, Rafael David Tinoco wrote:
> Definitely. Since PCS is a
** Changed in: pcs (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640923
Title:
pcs cluster auth does not generate "tokens" file
To manage notifications
** Bug watch added: Debian Bug tracker #847294
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847294
** Also affects: pcs (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847294
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
Cases:
https://bugs.launchpad.net/ubuntu/+source/pcs/+bug/1580035
https://bugs.launchpad.net/ubuntu/+source/pcs/+bug/1580045
https://bugs.launchpad.net/ubuntu/+source/pcs/+bug/1640923
https://bugs.launchpad.net/ubuntu/+source/pcs/+bug/1640919
Are all being fixed into:
Showing fixes for:
https://bugs.launchpad.net/ubuntu/+source/pcs/+bug/1580035
https://bugs.launchpad.net/ubuntu/+source/pcs/+bug/1580045
https://bugs.launchpad.net/ubuntu/+source/pcs/+bug/1640923
Okay, for, working in the upstream version (since i'll propose major
changes to the debian package
Regarding this statement:
> It seems like "pcs cluster auth" should exit with an error message if
it can't generate a tokens file.
I do agree with this statement. Tested latest version upstream and it
doesn´t generate any error message also. We can open a bug upstream and
monitor. This is
At least the errors are being put into /var/log/pcsd:
~$ sudo pcs cluster auth cluster01 cluster02
Username: hacluster
Password:
I, [2016-11-28T11:52:35.006533 #7817] INFO -- : Running:
/usr/sbin/corosync-cmapctl totem.cluster_name
I, [2016-11-28T11:52:35.006602 #7817] INFO -- : CIB USER:
Worst than that, if you don´t have corosync installed:
http://pastebin.ubuntu.com/23548460/
So, likely, corosync should be put as a dependency for pcs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
PCS cluster auth does not generate a tokens file when /etc/corosync.conf
is present, but still shows that authorization completed successfully.
->%-
lsb_release -rd
- Description: Ubuntu 16.04.1 LTS
- Release: 16.04
+
** Changed in: pcs (Ubuntu)
Assignee: (unassigned) => Rafael David Tinoco (inaddy)
** Changed in: pcs (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pcs (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640923
Title:
pcs
14 matches
Mail list logo
