On 01/23/2019 01:53 PM, Lentes, Bernd wrote:
>
> - On Jan 22, 2019, at 6:00 PM, kgaillot kgail...@redhat.com wrote:
>
>> On Tue, 2019-01-22 at 16:52 +0100, Lentes, Bernd wrote:
>
>>> Now the restart, which makes me trouble.
>>> Currently i want to restart the cluster manually, because i'm not
>
- On Jan 22, 2019, at 6:00 PM, kgaillot kgail...@redhat.com wrote:
> On Tue, 2019-01-22 at 16:52 +0100, Lentes, Bernd wrote:
>> Now the restart, which makes me trouble.
>> Currently i want to restart the cluster manually, because i'm not
>> completly familiar with pacemaker and a bit afra
Hi all,
The first v2.2.1 release candidate of the PAF resource agent for Pacemaker has
been released yesterday.
This is a bugfix release with no new features. We expect to release in about a
week.
The changelog since 2.2.0 includes:
* fix: Fix checking for notify=true, YanChii
* fix: forbid p
Hi Jonathan,
the resources will stay up. Resources do not depend on pcsd daemon
lifecycle.
Ivan
On 1/22/19 5:31 PM, Jonathan Hull wrote:
A quick question, this is on RHEL7. If I was to restart the pcs daemon
only (pcsd), such as is done automatically when changing the cert with
"pcs pcsd ce
A quick question, this is on RHEL7. If I was to restart the pcs daemon only
(pcsd), such as is done automatically when changing the cert with "pcs pcsd
certkey" will this also restart the cluster resources causing downtime or
do the resources stay up?
Thanks.
__
