+++ This bug is a downstream clone. The original bug is: +++
+++ bug 1568265 +++
======================================================================
Description of problem:
In executeCommand() in VdsNotRespondingTreatmentCommand.java, there is this initial if clause that aborts fencing:
if (!previousHostedEngineHost.isPreviousHostId(getVds().getId())
&& !new FenceValidator().isStartupTimeoutPassed()) {
log.error("Failed to run Fence script on vds '{}'.", getVdsName());
alertIfPowerManagementOperationSkipped(RESTART, null);
// If fencing can't be done and the host is the SPM, set storage-pool to non-operational
if (getVds().getSpmStatus() != VdsSpmStatus.None) {
setStoragePoolNonOperational();
}
return;
On entering the if clause, the host is not fenced and VDS_ALERT_FENCE_OPERATION_SKIPPED is logged. And VDS_ALERT_FENCE_OPERATION_SKIPPED="....It has no power management configured..."
I dont see that if clause testing for power management configured, Power management configured check on a different place.
The if clause evaluates DisableFenceAtStartupInSec and not fencing the HE host, IMHO this has nothing to do with power management enabled.
Am I missing something or this produces misleading logs?
Please improve logging, a separate message for each reason would be nice:
- HostedEngine (4.1+)
- DisableFenceAtStartup (4.1+)
- isInFenceFlow() (4.2+)
- Move VDS_ALERT_FENCE_OPERATION_SKIPPED
(Originally by Germano Veit Michel)
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2018:2318