Hi,
pcs-0.9 does not support pacemaker => 2.0.0. You can go with pcs-0.9 +
corosync < 3 + pacemaker 1.x OR pcs-0.10 + corosync 3.x + pacemaker 2.x.
Combination of corosync 2 + pacemaker 2 is not supported in any pcs
version, even though it may work to some degree.
Regards,
Tomas
Dne 03.
With that in mind, I'd suggest upgrading to a newer pcs version if
possible. If not, then you may have to do something more hack-y, like `pcs
status | grep '(.*:.*):'`.
On Wed, Feb 3, 2021 at 1:26 PM Reid Wahl wrote:
> Looks like pcs-0.9 isn't fully compatible with pacemaker >= 2.0.3.
> -
>
Looks like pcs-0.9 isn't fully compatible with pacemaker >= 2.0.3.
-
https://github.com/ClusterLabs/pcs/commit/0cf06b79f6dcabb780ee1fa7fee0565d73789329
The resource_status() function in older pcs versions doesn't match the
lines in the crm_mon output of newer pacemaker versions.
On Wed, Feb 3,
Hi Team,
In latest pacemaker version 2.0.5 we are not getting "pcs status resource"
command output but in older version we used to get the output.
Kindly let us know any already command to get pcs full list resource.
Latest Pacemaker version :
pacemaker-2.0.5 -->
