Re: [ClusterLabs] Pacemaker 1.1.16 - Release Candidate 1

On 11/03/2016 07:13 PM, Adam Spiers wrote: > Klaus Wenninger wrote: >> On 11/03/2016 05:28 PM, Adam Spiers wrote: >>> Ken Gaillot wrote: ClusterLabs is happy to announce the first release candidate for Pacemaker version 1.1.16. Source code is

Re: [ClusterLabs] Pacemaker 1.1.16 - Release Candidate 1

Klaus Wenninger wrote: > On 11/03/2016 05:28 PM, Adam Spiers wrote: > > Ken Gaillot wrote: > >> ClusterLabs is happy to announce the first release candidate for > >> Pacemaker version 1.1.16. Source code is available at: > >> > >>

Re: [ClusterLabs] pacemaker after upgrade from wheezy to jessie

> I'm guessing this change should be instantly written into the xml file? > If this is the case something is wrong, greping for validate gives the > old string back. We found some strange behavior when setting "validate-with" via cibadmin, corosync.log shows the successful transaction, issuing

Re: [ClusterLabs] Pacemaker 1.1.16 - Release Candidate 1

Ken Gaillot wrote: > ClusterLabs is happy to announce the first release candidate for > Pacemaker version 1.1.16. Source code is available at: > > https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-1.1.16-rc1 > > The most significant enhancements in this

Re: [ClusterLabs] Coming in 1.1.16: versioned resource parameters

> With a new feature in the current master branch, which will be part of > the next Pacemaker release, you will be able to specify different > resource parameters to be used with different versions of a resource agent. FYI, this feature is being held back to 1.1.17, due to a planned

Re: [ClusterLabs] [SECURITY] CVE-2016-7035 - pacemaker - improper IPC guarding

On 11/03/2016 06:03 AM, Jan Pokorný wrote: > Following issue is being publicly disclosed today; more information > regarding the release process will arrive later today and also this > is an opportunity to announce http://clusterlabs.org/wiki/Security > page that was intoduced to help keeping

[ClusterLabs] Fix in Pacemaker 1.1.15 retroactively assigned CVE-2016-7797

Hello all, Pacemaker 1.1.15, released earlier this year, contained a fix for a potential denial-of-service vulnerability in pacemaker_remote. This vulnerability has been retroactively assigned the Common Vulnerabilities and Exposures identifier CVE-2016-7797. This was mentioned in the 1.1.15

Re: [ClusterLabs] packmaker: After migrate a resource, changing resource non-unique param lead to resoruce restart

On 11/03/2016 02:01 AM, 李清硕 wrote: > Hi everyone, > I'm testing pacemaker resoruce live migration, in a simple test > environment with two virtual machines. > The resource is something encapsulated kvm, when i perfrom migrate, for > example, form node1 to node2, > i notice, the pacemaker invoke

Re: [ClusterLabs] pacemaker after upgrade from wheezy to jessie

> I'm going to guess you were using the experimental 1.1 schema as the > "validate-with" at the top of /var/lib/pacemaker/cib/cib.xml. Try > changing the validate-with to pacemaker-next or pacemaker-1.2 and see if > you get better results. Don't edit the file directly though; use the > cibadmin

Re: [ClusterLabs] pacemaker after upgrade from wheezy to jessie

> You'll want to switch your validate-with schema to a newer schema, and most > likely there will be one or two things that don't validate > anymore. There is the "crm configure upgrade" command, but if crmsh is > having problems you can call cibadmin directly: > > cibadmin --upgrade

[ClusterLabs] pacemaker after upgrade from wheezy to jessie

Hi, we just upgraded our nodes from wheezy 7.11 (pacemaker 1.1.7) to jessie (pacemaker 1.1.15, corosync 2.3.6). During the upgrade pacemaker was removed (rc) and reinstalled after from jessie-backports, same for crmsh. Now we are encountering multiple problems: First I checked the

Re: [ClusterLabs] Live migration not working on shutdown

On 11/02/2016 06:32 PM, Ken Gaillot wrote: > On 10/26/2016 06:12 AM, Rainer Nerb wrote: >> Hello all, >> >> we're currently testing a 2-node-cluster with 2 vms and live migration >> on CentOS 7.2 and Pacemaker 1.1.13-10 with disks on iSCSI-targets and >> migration via ssh-method. >> >> Live

[ClusterLabs] Q: (SLES11 SP4) Truncated lines in /var/log/pacemaker.log?

Hi! Looking at /var/log/pacemaker.log I got the impression that lines are truncated at 512 bytes. Is that true, and if so: Why? Pacemaker creates lines longer than that limit. For example a "cib: info: cib_perform_op: ++ /cib/status/node_state" usually exceeds that limit. Following some