Re: [ClusterLabs] New website design and new-new logo

[Digimer]

On 2017-09-20 07:53 PM, Ken Gaillot wrote:
> Hi everybody,
> 
> We've started a major update of the ClusterLabs web design. The main
> goal (besides making it look more modern) is to make the top-level more
> about all ClusterLabs projects rather than Pacemaker-specific. It's
> also much more mobile-friendly.
> 
> We've also updated our new logo -- Kristoffer Grönlund had a
> professional designer look at the one he created. I hope everyone likes
> the end result. It's simpler, cleaner and friendlier.
> 
> Check it out at https://clusterlabs.org/

This is excellent!

Can I recommend an additional category? It would be nice to have a
"Projects" link that provided a list of projects that fall under the
clusterlabs umbrella, with a brief blurb and a link to each.

Thanks for doing this! It's much more general now, which is great.

-- 
Digimer
Papers and Projects: https://alteeve.com/w/
"I am, somehow, less interested in the weight and convolutions of
Einstein’s brain than in the near certainty that people of equal talent
have lived and died in cotton fields and sweatshops." - Stephen Jay Gould

___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

[ClusterLabs] New website design and new-new logo

[Ken Gaillot]

Hi everybody,

We've started a major update of the ClusterLabs web design. The main
goal (besides making it look more modern) is to make the top-level more
about all ClusterLabs projects rather than Pacemaker-specific. It's
also much more mobile-friendly.

We've also updated our new logo -- Kristoffer Grönlund had a
professional designer look at the one he created. I hope everyone likes
the end result. It's simpler, cleaner and friendlier.

Check it out at https://clusterlabs.org/

-- 
Ken Gaillot 




___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] some resources move after recovery

[Ken Gaillot]

On Wed, 2017-09-20 at 10:08 +, Roberto Muñoz Gomez wrote:
> Hi,
> 
> 
> I don't know why if one of the two nodes is rebooted, when the node
> is back, some of the resources move to it despite default-resource-
> stickiness=100 and the resources have failcount=0 and there is no
> constraint influencing that change.
> 
> By some I mean sometimes 1, other 90, other 103...in a 900+ resource
> cluster.
> 
> The only clue I have is this line in the log:
> 
> pengine: info: native_color:    Resource o464rt cannot run
> anywhere
> 
> Is there any way I can "debug" this behaviour?

It's not very user-friendly, but you can get the most information from
the crm_simulate tool. Shortly past the above line in the log, there
will be a line like "Calculated transition ..., saving inputs in ..."
with a file path.

Grab that file, which has the entire state of the cluster at that point
in time. Run "crm_simulate -Ssx ". It will tell you what it
thinks the state of the nodes and resources were at that time, all the
scores that go into resource placement, and then the actions it thinks
need to be taken ("Transition Summary"). It will then simulate taking
those actions and show what the resulting new status would be.

It's not always obvious where the scores come from, but it does give
more information.

> 
> 
> Best Regards.
> ·
> Roberto Muñoz
> BME - Sistemas UNIX
> C/ Tramontana, 2 Bis. Edificio 2 - 1ª Planta
> 28230 Las Rozas, Madrid - España
> Tlfn: +34-917095778
> 
> 
> P Antes de imprimir, piensa en el MEDIO AMBIENTE
> AVISO LEGAL/DISCLAIMER
-- 
Ken Gaillot 




___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] Pacemaker 1.1.18 deprecation warnings

[Ken Gaillot]

On Wed, 2017-09-20 at 11:48 +0200, Ferenc Wágner wrote:
> Ken Gaillot  writes:
> 
> > * undocumented LRMD_MAX_CHILDREN environment variable
> > (PCMK_node_action_limit is the current syntax)
> 
> By the way, is the current syntax documented somewhere?  Looking at

Unfortunately not in its entirety (on the to-do list)

The crmd man page documents load-threshold and node-action-limit

> crmd/throttle.c, throttle_update_job_max() is only ever invoked with
> a
> NULL argument, so "Global preference from the CIB" isn't implemented
> either.  Or do I overlook something?

See crmd/control.c:config_query_callback() -- it calls
throttle_update_job_max() with the value of node-action-limit (a
cluster property that applies to all nodes, as opposed to
PCMK_node_action_limit which is an environment variable that applies
only to the local node)
-- 
Ken Gaillot 




___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

[ClusterLabs] some resources move after recovery

[Roberto Muñoz Gomez]

Hi,


I don't know why if one of the two nodes is rebooted, when the node is back, 
some of the resources move to it despite default-resource-stickiness=100 and 
the resources have failcount=0 and there is no constraint influencing that 
change.

By some I mean sometimes 1, other 90, other 103...in a 900+ resource cluster.

The only clue I have is this line in the log:

pengine: info: native_color:Resource o464rt cannot run anywhere

Is there any way I can "debug" this behaviour?


Best Regards.
·
Roberto Muñoz
BME - Sistemas UNIX
C/ Tramontana, 2 Bis. Edificio 2 - 1ª Planta
28230 Las Rozas, Madrid - España
Tlfn: +34-917095778



P Antes de imprimir, piensa en el MEDIO AMBIENTE
AVISO LEGAL/DISCLAIMER
___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] Pacemaker 1.1.18 deprecation warnings

[Ferenc Wágner]

Ken Gaillot  writes:

> * undocumented LRMD_MAX_CHILDREN environment variable
> (PCMK_node_action_limit is the current syntax)

By the way, is the current syntax documented somewhere?  Looking at
crmd/throttle.c, throttle_update_job_max() is only ever invoked with a
NULL argument, so "Global preference from the CIB" isn't implemented
either.  Or do I overlook something?
-- 
Thanks,
Feri

___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

[ClusterLabs] pcmk_remote evaluation (continued)

[Vladislav Bogdanov]

Hi,

as 1.1.17 received a lot of care in pcmk_remote, I decided to try it again
in rather big setup (less then previous, so I'm not hit by IPC disconnects 
here).

>From the first runs there are still some severe issues when cluster nodes are 
>fenced.

The following results are obtained by killing the DC node (md12k-3-srv) which 
was
hosting remote resources for nodes es7700-3-srv, es12kxe-3-srv and 
es12kxe-7-srv.
After the fence new DC (md12k-1-srv) has moved that resources the following way:
=
Sep 20 08:53:28 md12k-1-srv pengine[2525]:   notice: Movees12kxe-3-srv  
(Started md12k-3-srv -> md12k-4-srv)
Sep 20 08:53:28 md12k-1-srv pengine[2525]:   notice: Movees12kxe-7-srv  
(Started md12k-3-srv -> md12k-1-srv)
Sep 20 08:53:28 md12k-1-srv pengine[2525]:   notice: Movees7700-3-srv   
(Started md12k-3-srv -> md12k-2-srv)
=

* The first issue I found (and I expect that to be a reason for some other 
issues) is that
pacemaker_remote does not drop an old crmds' connection after new crmd connects.
As IPC proxy connections are in the hash table, there is a 50% chance that 
remoted tries to
reach an old crmd to f.e. proxy checks of node attributes when resources are 
reprobed.
That leads to timeouts of that resources' probes with consequent reaction from 
a cluster.
A solution here could be to drop old IPC proxy connection as soon as new one is 
established.

* I _suspect_ that the issue above could lead to following lines in a cluster 
node logs.
I didn't check, but I suspect that when remoted decides to disconnect an old 
connection
after fenced node goes up and TCP connections are reset - it disconnects a new 
one too.
At least this issue happens at the same time fenced node rejoins a cluster.
These logs are for the case no resources operate node attributes (I removed 
that resources
from the CIB and set a stickiness for all others).
=
Sep 20 08:55:41 md12k-1-srv crmd[11375]:error: Timed out (1 ms) while 
waiting for remote data
Sep 20 08:55:41 md12k-1-srv crmd[11375]:error: Unable to receive expected 
reply, disconnecting.
Sep 20 08:55:41 md12k-1-srv crmd[11375]:error: Remote lrmd server 
disconnected while waiting for reply with id 9823.
Sep 20 08:55:41 md12k-1-srv crmd[11375]:error: Unexpected disconnect on 
remote-node es12kxe-7-srv
Sep 20 08:55:41 md12k-1-srv crmd[11375]:error: Result of monitor operation 
for es12kxe-7-srv on md12k-1-srv: Error
Sep 20 08:55:41 md12k-1-srv crmd[11375]:error: Couldn't perform 
lrmd_rsc_info operation (timeout=0): -107: Success (0)
Sep 20 08:55:41 md12k-1-srv crmd[11375]:error: LRMD disconnected
Sep 20 08:55:41 md12k-1-srv crmd[11375]:error: Could not add resource 
ost0033-es03a to LRM es12kxe-7-srv
Sep 20 08:55:41 md12k-1-srv crmd[11375]:error: Invalid resource definition 
for ost0033-es03a
Sep 20 08:55:41 md12k-1-srv crmd[11375]:  warning: bad input   

Sep 20 08:55:41 md12k-1-srv crmd[11375]:  warning: bad input 
Sep 20 08:55:41 md12k-1-srv crmd[11375]:  warning: bad input   
Sep 20 08:55:41 md12k-1-srv crmd[11375]:  warning: bad input 
Sep 20 08:55:41 md12k-1-srv crmd[11375]:  warning: bad input 

Sep 20 08:55:41 md12k-1-srv crmd[11375]:  warning: bad input   
Sep 20 08:55:41 md12k-1-srv crmd[11375]:  warning: bad input 
Sep 20 08:55:41 md12k-1-srv crmd[11375]:  warning: bad input   

Sep 20 08:55:41 md12k-1-srv crmd[11375]:  warning: Resource ost0033-es03a no 
longer exists in the lrmd
Sep 20 08:55:41 md12k-1-srv crmd[11375]:  warning: Action 221 
(ost0033-es03a_monitor_0) on es12kxe-7-srv failed (target: 7 vs. rc: 6): Error
Sep 20 08:55:41 md12k-1-srv crmd[11375]:   notice: Transition aborted by 
lrm_rsc_op.ost0033-es03a_last_failure_0: Event failed
Sep 20 08:55:41 md12k-1-srv crmd[11375]:  warning: Action 221 
(ost0033-es03a_monitor_0) on es12kxe-7-srv failed (target: 7 vs. rc: 6): Error
Sep 20 08:55:41 md12k-1-srv crmd[11375]:error: Result of probe operation 
for ost0033-es03a on es12kxe-7-srv: Error
Sep 20 08:55:41 md12k-1-srv crmd[11375]:   notice: Transition aborted by 
operation es12kxe-3-srv_monitor_3 'create' on md12k-4-srv: Old event
...
ep 20 08:56:41 md12k-1-srv attrd[2524]:   notice: Node md12k-3-srv state is now 
member
Sep 20 08:56:41 md12k-1-srv cib[2511]:   notice: Node md12k-3-srv state is now 
member
Sep 20 08:56:41 md12k-1-srv pacemakerd[2398]:   notice: Node md12k-3-srv state 
is now member
Sep 20 08:56:41 md12k-1-srv crmd[11375]:   notice: Node md12k-3-srv state is 
now member
Sep 20 08:56:41 md12k-1-srv stonith-ng[2522]:   notice: Node md12k-3-srv state 
is now member
Sep 20 08:56:41 md12k-1-srv crmd[11375]:  warning: No reason to expect node 2 
to be down
Sep 20 08:56:41 md12k-1-srv crmd[11375]:   notice: Stonith/shutdown of 
md12k-3-srv not matched
=
I cannot check if that is a true until the first issue is fixed.

* There are repeated probe results with rc 6 (PCMK_OCF_NOT_CONFIGURED)
and 189 (PCMK_OCF_CONNECTION_DIED) if 

Re: [ClusterLabs] can't create master/slave resource

[Klaus Wenninger]

On 09/20/2017 10:40 AM, Tiemen Ruiten wrote:
> Thank you very much for the detailed explanation. We will look for
> another way to determine master/slave status of this application then.

What you still could try is to write kind of an ocf-wrapper for your
systemd-service
so that you can leave starting/stopping to systemd (controlled via
systemctl) and
do what is needed on top to control master/slave-state in the
ocf-Resource-Agent.
iirc there have been threads about creating ocf-wrappers of systemd-services
on this mailing-list.

Regards,
Klaus

>
> On 20 September 2017 at 09:20, Tomas Jelinek  > wrote:
>
>
>
> Dne 20.9.2017 v 09:03 Tomas Jelinek napsal(a):
>
> Hi,
>
> systemd resources cannot be used as master/slave resources. In
> order to use a resource as a master/slave, the resource must
> support promote and demote actions [1], which systemd
> resources don't.
>
> # pcs resource create test systemd:postfix
> # pcs resource master test
> # pcs cluster verify -V
>     error: native_unpack:    Resource test:0 is of type
> systemd and therefore cannot be used as a master/slave resource
>     error: create_child_clone:   Failed unpacking resource test
>     error: unpack_resources: Failed unpacking master
> test-master
> Errors found during check: config not valid
>
> You need to use an ocf resource agent (with promote and demote
> actions implemented) for your resource for this to work.
>
> Because the resource cannot be unpacked by pacemaker, it is
> not shown in the "pcs status" output - pcs doesn't get any
> info about it from pacemaker. This issue has been already
> discussed. Pacemaker will provide info when such errors occur
> so pcs will be able to display it. [2]
>
> The resource may not be running but it is still defined in the
> configuration:
> # pcs resource --full
>   Master: test-master
>    Resource: test (class=systemd type=postfix)
>     Operations: monitor interval=60 timeout=100
> (test-monitor-interval-60)
>     start interval=0s timeout=100
> (test-start-interval-0s)
>     stop interval=0s timeout=100
> (test-stop-interval-0s)
>
> That's why you get an error that the id already exists.
>
>
> I'm going to file a bug against pcs so it won't be possible to
> master/slave systemd resources as it is not supported anyway.
>
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1493416
> 
>
>
>
> Regards,
> Tomas
>
> [1]:
> 
> http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html-single/Pacemaker_Explained/index.html#_requirements_for_multi_state_resource_agents
> 
> 
>
> [2]: https://bugzilla.redhat.com/show_bug.cgi?id=1447951
> 
>
>
> Dne 19.9.2017 v 17:13 Tiemen Ruiten napsal(a):
>
> Hello,
>
> We have a 3-node cluster (CentOS 7.4) with several systemd
> resources configured. One of them I would like to create
> as a master/slave resource, so following the RedHat
> documentation:
>
> pcs resource create ivr systemd:japp@ivr - works, the
> service is started on one of the nodes.
> pcs resource master ivr-master ivr - doesn't work as
> expected: the service is stopped and the output of pcs
> resource show doesn't list it anymore. However, if I try
> the command again, I get an error saying the resource ivr
> already exists! I have to delete the resource and recreate
> it to get the service to run.
>
> pacemaker-libs-1.1.16-12.el7_4.2.x86_64
> pacemaker-cluster-libs-1.1.16-12.el7_4.2.x86_64
> pacemaker-1.1.16-12.el7_4.2.x86_64
> pacemaker-cli-1.1.16-12.el7_4.2.x86_64
> corosynclib-2.4.0-9.el7_4.2.x86_64
> corosync-2.4.0-9.el7_4.2.x86_64
>
> Am I doing something wrong?
>
> -- 
> Tiemen Ruiten
> Systems Engineer
> R Media
>
>
> ___
> Users mailing list: Users@clusterlabs.org
> 
> http://lists.clusterlabs.org/mailman/listinfo/users
> 
>
> Project Home: http://www.clusterlabs.org
> Getting started:
> 

Re: [ClusterLabs] can't create master/slave resource

[Tiemen Ruiten]

Thank you very much for the detailed explanation. We will look for another
way to determine master/slave status of this application then.

On 20 September 2017 at 09:20, Tomas Jelinek  wrote:

>
>
> Dne 20.9.2017 v 09:03 Tomas Jelinek napsal(a):
>
>> Hi,
>>
>> systemd resources cannot be used as master/slave resources. In order to
>> use a resource as a master/slave, the resource must support promote and
>> demote actions [1], which systemd resources don't.
>>
>> # pcs resource create test systemd:postfix
>> # pcs resource master test
>> # pcs cluster verify -V
>> error: native_unpack:Resource test:0 is of type systemd and
>> therefore cannot be used as a master/slave resource
>> error: create_child_clone:   Failed unpacking resource test
>> error: unpack_resources: Failed unpacking master test-master
>> Errors found during check: config not valid
>>
>> You need to use an ocf resource agent (with promote and demote actions
>> implemented) for your resource for this to work.
>>
>> Because the resource cannot be unpacked by pacemaker, it is not shown in
>> the "pcs status" output - pcs doesn't get any info about it from pacemaker.
>> This issue has been already discussed. Pacemaker will provide info when
>> such errors occur so pcs will be able to display it. [2]
>>
>> The resource may not be running but it is still defined in the
>> configuration:
>> # pcs resource --full
>>   Master: test-master
>>Resource: test (class=systemd type=postfix)
>> Operations: monitor interval=60 timeout=100 (test-monitor-interval-60)
>> start interval=0s timeout=100 (test-start-interval-0s)
>> stop interval=0s timeout=100 (test-stop-interval-0s)
>>
>> That's why you get an error that the id already exists.
>>
>>
>> I'm going to file a bug against pcs so it won't be possible to
>> master/slave systemd resources as it is not supported anyway.
>>
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1493416
>
>
>
>> Regards,
>> Tomas
>>
>> [1]: http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html-sing
>> le/Pacemaker_Explained/index.html#_requirements_for_multi_
>> state_resource_agents
>> [2]: https://bugzilla.redhat.com/show_bug.cgi?id=1447951
>>
>>
>> Dne 19.9.2017 v 17:13 Tiemen Ruiten napsal(a):
>>
>>> Hello,
>>>
>>> We have a 3-node cluster (CentOS 7.4) with several systemd resources
>>> configured. One of them I would like to create as a master/slave resource,
>>> so following the RedHat documentation:
>>>
>>> pcs resource create ivr systemd:japp@ivr - works, the service is
>>> started on one of the nodes.
>>> pcs resource master ivr-master ivr - doesn't work as expected: the
>>> service is stopped and the output of pcs resource show doesn't list it
>>> anymore. However, if I try the command again, I get an error saying the
>>> resource ivr already exists! I have to delete the resource and recreate it
>>> to get the service to run.
>>>
>>> pacemaker-libs-1.1.16-12.el7_4.2.x86_64
>>> pacemaker-cluster-libs-1.1.16-12.el7_4.2.x86_64
>>> pacemaker-1.1.16-12.el7_4.2.x86_64
>>> pacemaker-cli-1.1.16-12.el7_4.2.x86_64
>>> corosynclib-2.4.0-9.el7_4.2.x86_64
>>> corosync-2.4.0-9.el7_4.2.x86_64
>>>
>>> Am I doing something wrong?
>>>
>>> --
>>> Tiemen Ruiten
>>> Systems Engineer
>>> R Media
>>>
>>>
>>> ___
>>> Users mailing list: Users@clusterlabs.org
>>> http://lists.clusterlabs.org/mailman/listinfo/users
>>>
>>> Project Home: http://www.clusterlabs.org
>>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>>> Bugs: http://bugs.clusterlabs.org
>>>
>>>
>> ___
>> Users mailing list: Users@clusterlabs.org
>> http://lists.clusterlabs.org/mailman/listinfo/users
>>
>> Project Home: http://www.clusterlabs.org
>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>> Bugs: http://bugs.clusterlabs.org
>>
>
> ___
> Users mailing list: Users@clusterlabs.org
> http://lists.clusterlabs.org/mailman/listinfo/users
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>



-- 
Tiemen Ruiten
Systems Engineer
R Media
___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] can't create master/slave resource

[Tomas Jelinek]

Dne 20.9.2017 v 09:03 Tomas Jelinek napsal(a):

Hi,

systemd resources cannot be used as master/slave resources. In order to 
use a resource as a master/slave, the resource must support promote and 
demote actions [1], which systemd resources don't.


# pcs resource create test systemd:postfix
# pcs resource master test
# pcs cluster verify -V
    error: native_unpack:    Resource test:0 is of type systemd and 
therefore cannot be used as a master/slave resource

    error: create_child_clone:   Failed unpacking resource test
    error: unpack_resources: Failed unpacking master test-master
Errors found during check: config not valid

You need to use an ocf resource agent (with promote and demote actions 
implemented) for your resource for this to work.


Because the resource cannot be unpacked by pacemaker, it is not shown in 
the "pcs status" output - pcs doesn't get any info about it from 
pacemaker. This issue has been already discussed. Pacemaker will provide 
info when such errors occur so pcs will be able to display it. [2]


The resource may not be running but it is still defined in the 
configuration:

# pcs resource --full
  Master: test-master
   Resource: test (class=systemd type=postfix)
    Operations: monitor interval=60 timeout=100 (test-monitor-interval-60)
    start interval=0s timeout=100 (test-start-interval-0s)
    stop interval=0s timeout=100 (test-stop-interval-0s)

That's why you get an error that the id already exists.


I'm going to file a bug against pcs so it won't be possible to 
master/slave systemd resources as it is not supported anyway.


https://bugzilla.redhat.com/show_bug.cgi?id=1493416



Regards,
Tomas

[1]: 
http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html-single/Pacemaker_Explained/index.html#_requirements_for_multi_state_resource_agents 


[2]: https://bugzilla.redhat.com/show_bug.cgi?id=1447951


Dne 19.9.2017 v 17:13 Tiemen Ruiten napsal(a):

Hello,

We have a 3-node cluster (CentOS 7.4) with several systemd resources 
configured. One of them I would like to create as a master/slave 
resource, so following the RedHat documentation:


pcs resource create ivr systemd:japp@ivr - works, the service is 
started on one of the nodes.
pcs resource master ivr-master ivr - doesn't work as expected: the 
service is stopped and the output of pcs resource show doesn't list it 
anymore. However, if I try the command again, I get an error saying 
the resource ivr already exists! I have to delete the resource and 
recreate it to get the service to run.


pacemaker-libs-1.1.16-12.el7_4.2.x86_64
pacemaker-cluster-libs-1.1.16-12.el7_4.2.x86_64
pacemaker-1.1.16-12.el7_4.2.x86_64
pacemaker-cli-1.1.16-12.el7_4.2.x86_64
corosynclib-2.4.0-9.el7_4.2.x86_64
corosync-2.4.0-9.el7_4.2.x86_64

Am I doing something wrong?

--
Tiemen Ruiten
Systems Engineer
R Media


___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org



___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org


___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] can't create master/slave resource

[Tomas Jelinek]

Hi,

systemd resources cannot be used as master/slave resources. In order to 
use a resource as a master/slave, the resource must support promote and 
demote actions [1], which systemd resources don't.


# pcs resource create test systemd:postfix
# pcs resource master test
# pcs cluster verify -V
   error: native_unpack:Resource test:0 is of type systemd and 
therefore cannot be used as a master/slave resource

   error: create_child_clone:   Failed unpacking resource test
   error: unpack_resources: Failed unpacking master test-master
Errors found during check: config not valid

You need to use an ocf resource agent (with promote and demote actions 
implemented) for your resource for this to work.


Because the resource cannot be unpacked by pacemaker, it is not shown in 
the "pcs status" output - pcs doesn't get any info about it from 
pacemaker. This issue has been already discussed. Pacemaker will provide 
info when such errors occur so pcs will be able to display it. [2]


The resource may not be running but it is still defined in the 
configuration:

# pcs resource --full
 Master: test-master
  Resource: test (class=systemd type=postfix)
   Operations: monitor interval=60 timeout=100 (test-monitor-interval-60)
   start interval=0s timeout=100 (test-start-interval-0s)
   stop interval=0s timeout=100 (test-stop-interval-0s)

That's why you get an error that the id already exists.


I'm going to file a bug against pcs so it won't be possible to 
master/slave systemd resources as it is not supported anyway.


Regards,
Tomas

[1]: 
http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html-single/Pacemaker_Explained/index.html#_requirements_for_multi_state_resource_agents

[2]: https://bugzilla.redhat.com/show_bug.cgi?id=1447951


Dne 19.9.2017 v 17:13 Tiemen Ruiten napsal(a):

Hello,

We have a 3-node cluster (CentOS 7.4) with several systemd resources 
configured. One of them I would like to create as a master/slave 
resource, so following the RedHat documentation:


pcs resource create ivr systemd:japp@ivr - works, the service is started 
on one of the nodes.
pcs resource master ivr-master ivr - doesn't work as expected: the 
service is stopped and the output of pcs resource show doesn't list it 
anymore. However, if I try the command again, I get an error saying the 
resource ivr already exists! I have to delete the resource and recreate 
it to get the service to run.


pacemaker-libs-1.1.16-12.el7_4.2.x86_64
pacemaker-cluster-libs-1.1.16-12.el7_4.2.x86_64
pacemaker-1.1.16-12.el7_4.2.x86_64
pacemaker-cli-1.1.16-12.el7_4.2.x86_64
corosynclib-2.4.0-9.el7_4.2.x86_64
corosync-2.4.0-9.el7_4.2.x86_64

Am I doing something wrong?

--
Tiemen Ruiten
Systems Engineer
R Media


___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org



___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org