[ClusterLabs] (no subject)

[Ken Gaillot]

On 07/20/2017 12:21 AM, ArekW wrote:
> Hi, How to properly unset a value with pcs? Set to false or null gives error:
> 
> # pcs stonith update vbox-fencing verbose=false --force
> or
> # pcs stonith update vbox-fencing verbose= --force
> 
> Jul 20 07:14:11 nfsnode1 stonith-ng[11097]: warning: fence_vbox[3092]
> stderr: [ WARNING:root:Parse error: Ignoring option 'verbose' because
> it does not have value ]
> 
> To surpress the message I have to delete resource and recteate it
> without unwanted variable. I'am not sure if it concerns also other
> variables or it's just this one.

Pacemaker and pcs can handle empty values; in this case, it's the fence
agent itself that's generating the warning. The "stderr" in the log
means that the fence agent printed this in its standard error output,
and pacemaker is just passing that along in the logs.

The message doesn't cause any problems for pacemaker, and from the
message, it looks like it doesn't cause problems for the agent either,
so it's just an annoyance.

I don't see a reason it should print an error in this case, so it's
probably worthwhile to submit a bug report against fence_vbox to
silently treat empty options as defaults.