Re: [ClusterLabs] epic fail

2017-07-23 Thread Digimer 
On 2017-07-23 08:27 AM, Dmitri Maziuk wrote:
> So yesterday I ran yum update that puled in the new pacemaker and tried
> to restart it. The node went into its usual "can't unmount drbd because
> kernel is using it" and got stonith'ed in the middle of yum transaction.
> The end result: DRBD reports split brain, HA daemons don't start on
> boot, RPM database is FUBAR. I've had enough. I'm rebuilding this
> cluster as centos 6 + heartbeat R1.
> 
> Centos 7 + DRBD 8.4 + pacemaker + NFS server: FAIL. You have been warned.
> 
> Dima

Is DRBD set to 'fencing resource-and-stonith'? If so, then the only way
to get a split-brain is if something is configured wrong in pacemaker or
if something caused crm-fence-peer.sh to report success when it didn't
actually succeed...

-- 
Digimer
Papers and Projects: https://alteeve.com/w/
"I am, somehow, less interested in the weight and convolutions of
Einstein’s brain than in the near certainty that people of equal talent
have lived and died in cotton fields and sweatshops." - Stephen Jay Gould

___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] epic fail

2017-07-23 Thread Kristián Feldsam 
You can not update running cluster! First you need put node standby, check if 
all resources stopped and them do what you need. This was unfortunately your 
fail :(

S pozdravem Kristián Feldsam
Tel.: +420 773 303 353, +421 944 137 535
E-mail.: supp...@feldhost.cz

www.feldhost.cz - FeldHost™ – profesionální hostingové a serverové služby za 
adekvátní ceny.

FELDSAM s.r.o.
V rohu 434/3
Praha 4 – Libuš, PSČ 142 00
IČ: 290 60 958, DIČ: CZ290 60 958
C 200350 vedená u Městského soudu v Praze

Banka: Fio banka a.s.
Číslo účtu: 2400330446/2010
BIC: FIOBCZPPXX
IBAN: CZ82 2010  0024 0033 0446

> On 23 Jul 2017, at 14:27, Dmitri Maziuk  wrote:
> 
> So yesterday I ran yum update that puled in the new pacemaker and tried to 
> restart it. The node went into its usual "can't unmount drbd because kernel 
> is using it" and got stonith'ed in the middle of yum transaction. The end 
> result: DRBD reports split brain, HA daemons don't start on boot, RPM 
> database is FUBAR. I've had enough. I'm rebuilding this cluster as centos 6 + 
> heartbeat R1.
> 
> Centos 7 + DRBD 8.4 + pacemaker + NFS server: FAIL. You have been warned.
> 
> Dima
> 
> 
> ___
> Users mailing list: Users@clusterlabs.org
> http://lists.clusterlabs.org/mailman/listinfo/users
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org

___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] epic fail

2017-07-23 Thread Valentin Vidic 
On Sun, Jul 23, 2017 at 07:27:03AM -0500, Dmitri Maziuk wrote:
> So yesterday I ran yum update that puled in the new pacemaker and tried to
> restart it. The node went into its usual "can't unmount drbd because kernel
> is using it" and got stonith'ed in the middle of yum transaction. The end
> result: DRBD reports split brain, HA daemons don't start on boot, RPM
> database is FUBAR. I've had enough. I'm rebuilding this cluster as centos 6
> + heartbeat R1.

It seems you did not put the node into standby before the upgrade as it
still had resources running.  What was the old/new pacemaker version there?

-- 
Valentin

___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

[ClusterLabs] epic fail

2017-07-23 Thread Dmitri Maziuk 
So yesterday I ran yum update that puled in the new pacemaker and tried 
to restart it. The node went into its usual "can't unmount drbd because 
kernel is using it" and got stonith'ed in the middle of yum transaction. 
The end result: DRBD reports split brain, HA daemons don't start on 
boot, RPM database is FUBAR. I've had enough. I'm rebuilding this 
cluster as centos 6 + heartbeat R1.


Centos 7 + DRBD 8.4 + pacemaker + NFS server: FAIL. You have been warned.

Dima


___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] [ClusterLabs Developers] [HA/ClusterLabs Summit] Key-Signing Party, 2017 Edition

2017-07-23 Thread Adam Spiers 

Hi Jan :-)

Jan Pokorný  wrote:

Hello cluster masters :-)

as there's little less than 7 weeks left to "The Summit" meetup
(), it's about time to get the ball
rolling so we can voluntarily augment the digital trust amongst
us the attendees, on OpenGPG basis.

Doing that, we'll actually establish a tradition since this will
be the second time such event is being kicked off (unlike the birds
of the feather gathering itself, was edu-feathered back then):

 
 

If there are no objections, yours truly will conduct this undertaking.


Awesome, thanks for volunteering to do this!

[snipped]


So, going to attend summit and want your key signed while reciprocally
spreading the web of trust?
Awesome, let's reuse the steps from the last time:

Once you have a key pair (and provided that you are using GnuPG),
please run the following sequence:

   # figure out the key ID for the identity to be verified;
   # IDENTITY is either your associated email address/your name
   # if only single key ID matches, specific key otherwise
   # (you can use "gpg -K" to select a desired ID at the "sec" line)
   KEY=$(gpg --with-colons 'IDENTITY' | grep '^pub' | cut -d: -f5)


AFAICS this has two problems: it's missing a --list-key option,
and it doesn't handle multiple matches for 'IDENTITY'.  So to make it
choose the newest key if there are several:

   read IDENTITY
   KEY=$(gpg --with-colons --list-key "$IDENTITY" | grep '^pub' |
 sort -t: -nr -k6 | head -n1 | cut -d: -f5)

HTH,
Adam


signature.asc
Description: Digital signature
___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org