*** This bug is a duplicate of bug 1580045 ***
https://bugs.launchpad.net/bugs/1580045
This bug uncovers more issues than just the IP binding issue (which is
easy to work-around). There's also the issue of /var/lib/pcsd/tokens not
being written into and the way that pcs cluster setup hangs.
-
*** This bug is a duplicate of bug 1580045 ***
https://bugs.launchpad.net/bugs/1580045
I've just looked at the other bugs that Rafael is working on and they
cover the other issues in this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
*** This bug is a duplicate of bug 1580045 ***
https://bugs.launchpad.net/bugs/1580045
I'm working on:
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.
It's actually a package breaker. A fresh install:
apt-get install pcs fence-agents ldirectord
fails. The file mentioned above that needs removing corosync.conf, prevents apt
from a successful install. Touching that to make it empty allows the install
to complete. Which, apparently, breaks the t
Mariusz' comments are spot on to fix this issue. Actually this bug
should be splitted in two parts:
- Fix token/auth generation for "pcs cluster auth" (/var/lib/pcsd/tokens
is not updated unless a set of prerequisites are met)
- Cluster configuration hangs during cleanup (e.g., "pcs cluster setup
Update on running pcs 0.9.151-1 on Ubuntu 16.04.
1. pacemaker and especially corosync must be stopped:
systemctl stop pacemaker corosync
2. Remove (or rename) /etc/corosync/corosync.conf
Without that "pcs cluster auth" won't create "tokens" file.
3. Modify /usr/lib/python2.7/dist-packages/pcs/
Yes, I confirm. There's no "tokens" file.
Only these:
root@u16a:~# ls /var/lib/pcsd/
pcsd.cookiesecret pcsd.crt pcsd.key pcs_users.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1584365
Title:
Hello,
I can confirm that after changing ssl.rb when i authenticate nothing gets
written to tokens.
I was able to workaround problem doing following steps:
1. configured corosync on each node in cluster (got 3 nodes):
totem {
version: 2
secauth: off
cluster_name: openstack
transp
@Mariusz - it sounds like /var/lib/pcsd/tokens still isn't getting
written out by running "pcs cluster auth". Can you confirm that?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1584365
Title:
pcs c
I tested pcs 0.9.151-1 (amd64 binary from Ubuntu yakkety) on Ubuntu 16.04.
pcsd binds to IPv4 now and doesn't require orderedhash gem, but authentication
still doesn't seem to work.
root@u16a:~# pcs cluster auth u16a u16b -u hacluster -p password ; echo $?
u16a: Authorized
u16b: Authorized
0
roo
Unfortunately, I couldn't get a pacemaker cluster to work on Ubuntu (I
instead used ocfs to provide a clustered filesystem) so I'm no longer in
a position to test this.
However, when I was tangling with it, I managed to get pcsd to bind to
IPv4 but there's still the problem with it not writing out
This could be related to Bug#1580045 pcsd does only bind to IPv6, now
patched in Debian package 0.9.151-1 so you can test this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1584365
Title:
pcs clust
** 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.
https://bugs.launchpad.net/bugs/1584365
Title:
pcs cluster auth unable to connect
To manage notifications about this bug
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/1584365
Title:
pcs cl
Dagnammit - "pcs cluster auth" doesn't write out /var/lib/pcsd/tokens so
anything I try to do with it afterwards just fails.
So, although "pcs cluster auth" returns "authorized", it doesn't
actually do its job.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I got this working after working around two other bugs.
"systemctl pcsd start" fails with ruby errors
(/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in
`required`) that can be fixed by running:
gem install orderedhash
After that, there's the problem with Ruby binding to the IPv6 int
Okay, looks like this isn't necessarily just an Ubuntu bug. I've since
had the same problems with running "pcs cluster auth" on RHEL7. It looks
like my test (see above) was using 127.0.0.1 as the ip address which
does work on both Ubuntu and RHEL7.
After lots of investigation, it looks like having
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1584365
Title:
pcs cluster auth unable to connect
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu
** Package changed: ubuntu => pcs (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1584365
Title:
pcs cluster auth unable to connect
To manage notifications about this bug go to:
https://bugs
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
20 matches
Mail list logo
