[ClusterLabs] multiple resources - pgsqlms - and IP(s)

[lejeczek]

On 03/01/2023 21:44, Ken Gaillot wrote:
> On Tue, 2023-01-03 at 18:18 +0100, lejeczek via Users wrote:
>> On 03/01/2023 17:03, Jehan-Guillaume de Rorthais wrote:
>>> Hi,
>>>
>>> On Tue, 3 Jan 2023 16:44:01 +0100
>>> lejeczek via Users <users at clusterlabs.org> wrote:
>>>
>>>> To get/have Postgresql cluster with 'pgsqlms' resource, such
>>>> cluster needs a 'master' IP - what do you guys do when/if
>>>> you have multiple resources off this agent?
>>>> I wonder if it is possible to keep just one IP and have all
>>>> those resources go to it - probably 'scoring' would be very
>>>> tricky then, or perhaps not?
>>> That would mean all promoted pgsql MUST be on the same node at any
>>> time.
>>> If one of your instance got some troubles and need to failover,
>>> *ALL* of them
>>> would failover.
>>>
>>> This imply not just a small failure time window for one instance,
>>> but for all
>>> of them, all the users.
>>>
>>>> Or you do separate IP for each 'pgsqlms' resource - the
>>>> easiest way out?
>>> That looks like a better option to me, yes.
>>>
>>> Regards,
>> Not related - Is this an old bug?:
>>
>> -> $ pcs resource create pgsqld-apps ocf:heartbeat:pgsqlms
>> bindir=/usr/bin pgdata=/apps/pgsql/data op start timeout=60s
>> op stop timeout=60s op promote timeout=30s op demote
>> timeout=120s op monitor interval=15s timeout=10s
>> role="Master" op monitor interval=16s timeout=10s
>> role="Slave" op notify timeout=60s meta promotable=true
>> notify=true master-max=1 --disable
>> Error: Validation result from agent (use --force to override):
>>     ocf-exit-reason:You must set meta parameter notify=true
>> for your master resource
>> Error: Errors have occurred, therefore pcs is unable to continue
> pcs now runs an agent's validate-all action before creating a resource.
> In this case it's detecting a real issue in your command. The options
> you have after "meta" are clone options, not meta options of the
> resource being cloned. If you just change "meta" to "clone" it should
> work.
Nope. Exact same error message.
If I remember correctly there was a bug specifically 
pertained to 'notify=true'
I'm on C8S with resource-agents-paf-4.9.0-35.el8.x86_64.