Open BlackZork opened 1 year ago
fence_xvm -H vmname -o monitor does nothing for tcp multicast.
fence_xvm -H vmname -o monitor
This causes pacemaker to assume that stonith resource is always ok, regardless if it is configured correctly or not.
From quick look at the code it seems that it is not implemented.
The monitor action should only report if it cant connect to fence_virtd or similar errors (so Pacemaker can show running, failed, etc).
If you want the status of a VM you'll have to use -o status.
fence_xvm -H vmname -o monitor
does nothing for tcp multicast.This causes pacemaker to assume that stonith resource is always ok, regardless if it is configured correctly or not.
From quick look at the code it seems that it is not implemented.