[Pacemaker] again "return code", now in crm_attribute

Andrey Groshev greenx at yandex.ru
Wed Dec 18 07:55:23 EST 2013


Hi, Andrew and ALL.

I'm sorry, but I again found an error. :)
Crux of the problem:

# crm_attribute --type crm_config --attr-name stonith-enabled --query; echo $?
scope=crm_config  name=stonith-enabled value=true
0

# crm_attribute --type crm_config --attr-name stonith-enabled --update firstval ; echo $?
0

# crm_attribute --type crm_config --attr-name stonith-enabled --query; echo $?
scope=crm_config  name=stonith-enabled value=firstval
0

# crm_attribute --type crm_config --attr-name stonith-enabled  --update secondval --lifetime=reboot ; echo $?
0

# crm_attribute --type crm_config --attr-name stonith-enabled --query; echo $?
scope=crm_config  name=stonith-enabled value=firstval
0

# crm_attribute --type crm_config --attr-name stonith-enabled  --update thirdval --lifetime=forever ; echo $?
0

# crm_attribute --type crm_config --attr-name stonith-enabled --query; echo $?
scope=crm_config  name=stonith-enabled value=firstval
0

Ie if specify the lifetime of an attribute, then a attribure is not updated.

If impossible setup the lifetime of the attribute when it is installing, it must be return an error.

And if possible then the value should be established.
In general, something is wrong.
Denser unfortunately not yet looked, because I struggle with "STONITH" :)

P.S. Andrew! Late to congratulate you on your new addition to the family. 
This fine time - now you will have toys which was not in your childhood.




More information about the Pacemaker mailing list