Hi Ken/Team,
For us straight forward issue we are able to reproduce continuously, So please
provide fix as soon as possible.
Thanks and Regards,
S Sathish S
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
On 13/07/2023 17:33, Ken Gaillot wrote:
On Wed, 2023-07-12 at 21:08 +0200, lejeczek via Users wrote:
Hi guys.
I have a fresh new 'galera' clone and that one would not start &
cluster says:
...
INFO: Waiting on node to report database status before Master
instances can start.
...
Is that
On Thu, 2023-07-13 at 09:58 +, S Sathish S via Users wrote:
> Hi Team,
>
> Problem Statement : we are trying to remove node on pcs cluster, post
> execution also still crm_node
> it is removed node is listing as lost node.
>
> we have checked corosync.conf file it is removed but still it
On Wed, 2023-07-12 at 21:08 +0200, lejeczek via Users wrote:
> Hi guys.
>
> I have a fresh new 'galera' clone and that one would not start &
> cluster says:
> ...
> INFO: Waiting on node to report database status before Master
> instances can start.
> ...
>
> Is that only for newly created
On 13/07/23 09:45 +0200, Oyvind Albrigtsen wrote:
On 12/07/23 12:57 +, Windl, Ulrich wrote:
Hi!
Some time ago, I had been asking for an improved fencing agent specification,
because the existing documents made it impossible for me to write a fencing
agent. I guess with such
Hi Team,
Problem Statement : we are trying to remove node on pcs cluster, post execution
also still crm_node
it is removed node is listing as lost node.
we have checked corosync.conf file it is removed but still it is displaying on
crm_node -l.
[root@node1 ~]# pcs cluster node remove node2
On 12/07/23 12:57 +, Windl, Ulrich wrote:
Hi!
Some time ago, I had been asking for an improved fencing agent specification,
because the existing documents made it impossible for me to write a fencing
agent. I guess with such documentation, the questions below could have been
answered as
