2019年7月18日(木) 22:42 Jan Pokorný :
> On 18/07/19 18:08 +0900, 井上和徳 wrote:
> > 'pcs config export' fails in RHEL 8.0 environment because clufter
> > does not support Corosync 3 (Camelback).
> > How is the state of progress? https://pagure.io/clufter/issue/4
>
> As much as I'd want to, time budget
That's it! Thanks, I haven't seen it before.
Missatge de Digimer del dia ds., 13 de jul. 2019 a les
1:57:
> On 2019-07-12 6:03 p.m., Josep Maria Viñolas wrote:
> > Hi,
> >
> > I don't know if it is possible to decide to start resource A in one node
> > and then start another resource B avoiding
On 18/07/19 18:08 +0900, 井上和徳 wrote:
> 'pcs config export' fails in RHEL 8.0 environment because clufter
> does not support Corosync 3 (Camelback).
> How is the state of progress? https://pagure.io/clufter/issue/4
As much as I'd want to, time budget hasn't been allocated for this,
pacemaker and
On 17/07/19 19:07 +, Gershman, Vladimir wrote:
> This would be for the Pacemaker.
>
> Seems like the alerts in the link you sent, refer to numeric codes,
> so where would I see all the codes and their meanings ? This would
> allow a way to select what I need to monitor.
Unfortunately, we
Hi,
'pcs config export' fails in RHEL 8.0 environment because clufter does not
support Corosync 3 (Camelback).
How is the state of progress? https://pagure.io/clufter/issue/4
[root@r80-1 ~]# cat /etc/redhat-release
Red Hat Enterprise Linux release 8.0 (Ootpa)
[root@r80-1 ~]# dnf list | grep -E
