Closed HideoYamauchi closed 4 years ago
Oh. That's not good.
I'll make a patch to fix it.
The patch is intended to make it not timeout when run from Pacemaker, so Pacemakers timeout for the fence device will be used instead by default.
I've made a patch to solve this issue. See PR linked above.
Hi oalbrigt,
Thanks for your comment.
Okay! I will check your patch tomorrow.
Best Regards, Hideo Yamauchi.
Hi oalbrigt,
I have confirmed that this fix(PR#359) works correctly. I also understand that this fix is not to skip the verification process, but to run it indefinitely and leave the timeout to Pacemaker.
Close this issue.
Many thanks, Hideo Yamauchi.
Hi All,
The details are unknown, but the following PR has been included in master.
This fix currently fails with the reboot action.
Maybe other fence_agents will also fail.
This is because the async_set_multi_power_fn() process returns False with an off operation.
Therefore, the on operation at the time of reboot operation is not executed. As a result, the reboot operation also fails.
I think it is very dangerous not to check the off status during the off operation, including the reboot operation. Shouldn't the on state (power-timeout) be skipped only when the on operation is performed?
My point may be wrong, as future changes to the Pacemaker spec may be relevant.
Was this change due to consideration of future specifications when combined with Pacemaker?
Best Regards, Hideo Yamauchi.