Re: [ClusterLabs] Antw: [EXT] Feedback wanted: OCF Resource Agent API 1.1 proposed for adoption

On Wed, Mar 10, 2021 at 12:20 AM Ulrich Windl < ulrich.wi...@rz.uni-regensburg.de> wrote: > >>> Ken Gaillot schrieb am 10.03.2021 um 00:07 in > Nachricht > : > > Hi all, > > > > After many false starts over the years, we finally have a proposed 1.1 > > version of the resource agent standard. > >

[ClusterLabs] "interesting error" with VirtualDomain and libvirt

Hi! I just had an "interesting error" with VirtualDomain in SLES15 SP2: On node h18 the configuration file for the VM was missing, but still the VM could be live-migrated to h18 a few days ago. When today the VM was to be restarted, shutdown worked correctly also, but the start attempt failed

Re: [ClusterLabs] pacemaker-2.0.x version support on “RHEL 7” OS

Hi Ken/Team, We are using pacemaker software from Clusterlab upstream with version pacemaker 2.0.2 in our RHEL 7 system. So for fixing the CVE’s CVE-2020-25654 we don’t want to downgrade to lower version of pacemaker 1.x hence we are trying to build latest pcs-0.10 version from upstream source

Re: [ClusterLabs] Antw: [EXT] Feedback wanted: OCF Resource Agent API 1.1 proposed for adoption

Ulrich Windl napsal(a): Ken Gaillot schrieb am 10.03.2021 um 00:07 in Nachricht : Hi all, After many false starts over the years, we finally have a proposed 1.1 version of the resource agent standard. Discussion is invited here and/or on the pull request:

[ClusterLabs] Antw: Re: Antw: [EXT] Feedback wanted: OCF Resource Agent API 1.1 proposed for adoption

>>> Reid Wahl schrieb am 10.03.2021 um 09:34 in Nachricht : ... > Besides, we can still get our point across with terms like > "promoted/unpromoted" :) I see, but wouldn't "ban" be another candidate? STONITH? fencing? killing? executing? throttling? ;-) Reagdrs, Ulrich P.S: Hope the new

[ClusterLabs] Antw: [EXT] Feedback wanted: OCF Resource Agent API 1.1 proposed for adoption

>>> Ken Gaillot schrieb am 10.03.2021 um 00:07 in Nachricht : > Hi all, > > After many false starts over the years, we finally have a proposed 1.1 > version of the resource agent standard. > > Discussion is invited here and/or on the pull request: > >

[ClusterLabs] Notice: deleting a cloned primitive with crm shell 4.1.0

Hi! While cleaning up an old cluster I noticed that crm shell announces automatic operations, but it does not announce that the clone is being deleted when deleting the primitive that was cloned. Example (where it works): crm(live/h02)configure# delete cln_cfs_locks INFO: modified

Re: [ClusterLabs] pacemaker-2.0.x version support on “RHEL 7” OS

Hi, The same principles apply to both pcs and pacemaker (and most probably the whole cluster stack). Red Hat only supports the packages it provides, which is pcs-0.9 series in RHEL 7. Even if you manage to install ruby 2.2.0+ and python 3.6+ on RHEL 7 hosts and build and run pcs-0.10 on

Re: [ClusterLabs] Notice: deleting a cloned primitive with crm shell 4.1.0

Hi Ulrich, Could you please give your output of "crm configure show"? I cannot catch up what these IDs represent Thanks Regards, xin From: Users on behalf of Ulrich Windl Sent: Wednesday, March 10, 2021 9:14 PM To: users@clusterlabs.org Subject:

Re: [ClusterLabs] pacemaker-2.0.x version support on “RHEL 7” OS

On Wed, 2021-03-10 at 07:15 +, S Sathish S wrote: > Hi Ken/Team, > > We are using pacemaker software from Clusterlab upstream with version > pacemaker 2.0.2 in our RHEL 7 system. So for fixing the CVE’s CVE- > 2020-25654 we don’t want to downgrade to lower version of pacemaker > 1.x hence we

[ClusterLabs] Antw: [EXT] Re: Notice: deleting a cloned primitive with crm shell 4.1.0

>>> Xin Liang schrieb am 10.03.2021 um 15:37 in Nachricht > Hi Ulrich, > > Could you please give your output of "crm configure show"? I cannot catch up > what these IDs represent Hi! First, after deletion there's not much "configure show" can tell you. Second the problem was where no INFO: