[ClusterLabs] last man - issue

[Tomas Jelinek]

Lejeczek,

Thanks for raising this. We'll improve the error message to make it 
clear that the cluster needs to be stopped in order to proceed.

Tomas


Dne 24. 07. 23 v 14:22 Michal Pospíšil (he / him) napsal(a):
> Hello all,
>
> One more useful link that I forgot to include in my original reply - 
> list of corosync options and when it is possible to update them: 
> https://github.com/corosync/corosync/wiki/Config-file-values
>
>
> Cheers,
> Michal
>
> On Mon, 24 Jul 2023 at 13:04, Michal Pospíšil (he / him) 
> <mpospisi at redhat.com> wrote:
>
>     Hi lejeczek,
>
>     Unfortunately, that command shouldn't work in this situation. The
>     problem is that the cluster (corosync) is running. From the man page:
>
>     update [auto_tie_breaker=[0|1]] [last_man_standing=[0|1]]
>     [last_man_standing_window=[<time in ms>]] [wait_for_all=[0|1]]
>                  Add, remove or change quorum options. At least one
>     option must be specified. Unspecified options will be kept
>     unchanged. If you wish to remove an option, set it to  empty
>      value,  i.e.
>                  'option_name='. Options are documented in corosync's
>     votequorum(5) man page. *Requires the cluster to be stopped.*
>
>     The output looks correct. More inline...
>
>     On Sat, 22 Jul 2023 at 13:44, lejeczek via Users
>     <users at clusterlabs.org> wrote:
>
>         Hi guys.
>
>         That below should work, right?
>
>         -> $ pcs quorum update last_man_standing=1 --skip-offline
>         Checking corosync is not running on nodes...
>
>
>     Corosync cannot be running to perform the requested corosync.conf
>     update.
>
>         Warning: Unable to connect to dzien (Failed to connect to
>         dzien port 2224: No route to host)
>
>         Warning: dzien: Unable to check if corosync is not running
>
>
>     Because of `--skip-offline`, these two messages are warnings, not
>     errors.
>
>         Error: swir: corosync is running
>         Error: whale: corosync is running
>
>
>     Turns out corosync is running on two other nodes, this is why pcs
>     refuses to continue. You have to stop the cluster, unfortunately.
>
>         Error: Errors have occurred, therefore pcs is unable to continue
>
>         if it should, why does it not or what else am I missing?
>
>         many thanks, L
>
>         _______________________________________________
>         Manage your subscription:
>         https://lists.clusterlabs.org/mailman/listinfo/users
>
>         ClusterLabs home: https://www.clusterlabs.org/
>
>
>
>     Cheers,
>     Michal
>     -- 
>
>     MICHAL POSPISIL
>     He / Him / His
>
>     Associate Software Engineer
>
>     RHEL HA Cluster - PCS
>
>     Red Hat Czech, s.r.o. <https://www.redhat.com>
>     Purkyňova 97b, 612 00 Brno
>
>     mpospisi at redhat.com IRC: mpospisi
>
>     <https://www.redhat.com>
>
>
>
> -- 
>
> MICHAL POSPISIL
> He / Him / His
>
> Associate Software Engineer
>
> RHEL HA Cluster - PCS
>
> Red Hat Czech, s.r.o. <https://www.redhat.com>
> Purkyňova 97b, 612 00 Brno
>
> mpospisi at redhat.com IRC: mpospisi
>
> <https://www.redhat.com>
>
>
> _______________________________________________
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
>
> ClusterLabs home:https://www.clusterlabs.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20230725/3647a817/attachment.htm>