[ClusterLabs] cluster okey but errors when tried to move resource - ?

[lejeczek]

On 09/06/2023 09:04, Reid Wahl wrote:
> On Thu, Jun 8, 2023 at 10:55 PM lejeczek via Users
> <users at clusterlabs.org> wrote:
>>
>>
>> On 09/06/2023 01:38, Reid Wahl wrote:
>>> On Thu, Jun 8, 2023 at 2:24 PM lejeczek via Users <users at clusterlabs.org> wrote:
>>>>
>>>>> Ouch.
>>>>>
>>>>> Let's see the full output of the move command, with the whole CIB that
>>>>> failed to validate.
>>>>>
>>>> For a while there I thought perhaps it was just that one
>>>> pglsq resource, but it seems that any - though only a few
>>>> are set up - (only clone promoted?)resource fails to move.
>>>> Perhaps primarily to do with 'pcs'
>>>>
>>>> -> $ pcs resource move REDIS-clone --promoted podnode3
>>>> Error: cannot move resource 'REDIS-clone'
>>>>       1 <cib crm_feature_set="3.17.4"
>>>> validate-with="pacemaker-3.6" epoch="8212" num_updates="0"
>>>> admin_epoch="0" cib-last-written="Thu Jun  8 21:59:53 2023"
>>>> update-origin="podnode1" update-client="crm_attribute"
>>>> have-quorum="1" update-user="root" dc-uuid="1">
>>> This is the problem: `validate-with="pacemaker-3.6"`. That old schema
>>> doesn't support role="Promoted" in a location constraint. Support
>>> begins with version 3.7 of the schema:
>>> https://github.com/ClusterLabs/pacemaker/commit/e7f1424df49ac41b2d38b72af5ff9ad5121432d2.
>>>
>>> You'll need at least Pacemaker 2.1.0.
>> I have:
>> corosynclib-3.1.7-1.el9.x86_64
>> corosync-3.1.7-1.el9.x86_64
>> pacemaker-schemas-2.1.6-2.el9.noarch
>> pacemaker-libs-2.1.6-2.el9.x86_64
>> pacemaker-cluster-libs-2.1.6-2.el9.x86_64
>> pacemaker-cli-2.1.6-2.el9.x86_64
>> pacemaker-2.1.6-2.el9.x86_64
>> pcs-0.11.5-2.el9.x86_64
>> pacemaker-remote-2.1.6-2.el9.x86_64
>> and the reset is Centos 9 up-to-what-is-in-repos
> If all your cluster nodes are at those versions, try `pcs cluster cib-upgrade`
>
>
'cib-upgrade' might be a fix for this "issue" - but should 
it not happen at rpm update time?
Differently but still 'move' errored out:
-> $ pcs resource move REDIS-clone --promoted podnode2
Location constraint to move resource 'REDIS-clone' has been 
created
Waiting for the cluster to apply configuration changes...
Location constraint created to move resource 'REDIS-clone' 
has been removed
Waiting for the cluster to apply configuration changes...
Error: resource 'REDIS-clone' is promoted on node 
'podnode3'; unpromoted on nodes 'podnode1', 'podnode2'
Error: Errors have occurred, therefore pcs is unable to continue

Then a node-promted-resource going into 'standby' or being 
rebooted - for first/one time - seemed to "fix" 'move'.
-> $ pcs resource move REDIS-clone --promoted podnode2
Location constraint to move resource 'REDIS-clone' has been 
created
Waiting for the cluster to apply configuration changes...
Location constraint created to move resource 'REDIS-clone' 
has been removed
Waiting for the cluster to apply configuration changes...
resource 'REDIS-clone' is promoted on node 'podnode2'; 
unpromoted on nodes 'podnode1', 'podnode3'

quite puzzling, sharing in case others experience this/similar.
thanks, L.