Pacemaker error to start fence_ipmilan because of incorrect password

Solution Verified - Updated -

Environment

  • Red Hat Openstack Platform 16.2

Issue

Pacemaker error to start fence_ipmilan Unable to obtain correct plug status or plug is not available due to incorrect password in fencing.yaml.

Resolution

  1. Validate the password and test in a direct command.
[root@controller1 ~]# fence_ipmilan -a <ip addr/hostname of ipmi device> -l <login> -p <password> -o status -P
Status: ON

  1. Compare the password used in the command with the password in fencing.yaml and update the template file. It should be same but in quotes if there's special characters as $.

  2. Run a overcloud deploy to update the environment or run the command below for each fence_ipmilan device.

pcs stonith update <stonith-fence_ipmilan-resource> passwd='<password>'

Root Cause

Password was incorrect in the template fencing.yaml because of a typo because this parameter accepts special characters just using quotes.

Diagnostic Steps

  1. Test the password and the connection to the device with the command below. It should return in few seconds that the device is ON. If not, continue troubleshooting
[root@controller1 ~]# time fence_ipmilan -a <ip addr/hostname of ipmi device> -l <login> -p <password> -o status -P
Status: ON
  1. Check pacemaker log for the error Unable to obtain correct plug status or plug is not available.
Jan 01 01:01:12 controller1 pacemaker-fenced[8880]: warning: fence_ipmilan[888864] stderr: [ 2024-01-01 01:01:12,203 ERROR: Failed: Unable to obtain correct plug status or plug is not available ]
  1. Confirm that the cause is not lanplus configuration.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments