Fencing fails with a delay attribute that includes "s" (or any non-integer value)
Issue
- After implementing a delay on one or more of our stonith resources, we are seeing fence failures.
- In the logs, the failures look like the following:
hostname stonith-ng[33888]: warning: fence_ipmilan[50215] stderr: [ Traceback (most recent call last): ]
hostname stonith-ng[33888]: warning: fence_ipmilan[50215] stderr: [ File "/usr/sbin/fence_ipmilan", line 199, in <module> ]
hostname stonith-ng[33888]: warning: fence_ipmilan[50215] stderr: [ main() ]
hostname stonith-ng[33888]: warning: fence_ipmilan[50215] stderr: [ File "/usr/sbin/fence_ipmilan", line 182, in main ]
hostname stonith-ng[33888]: warning: fence_ipmilan[50215] stderr: [ run_delay(options) ]
hostname stonith-ng[33888]: warning: fence_ipmilan[50215] stderr: [ File "/usr/share/fence/fencing.py", line 971, in run_delay ]
hostname stonith-ng[33888]: warning: fence_ipmilan[50215] stderr: [ time.sleep(int(options["--delay"])) ]
hostname stonith-ng[33888]: warning: fence_ipmilan[50215] stderr: [ ValueError: invalid literal for int() with base 10: '10s' ]
Environment
- Red Hat Enterprise Linux 6, 7, or 8 (with the High Availability Add-on)
- Pacemaker
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.