Bug 1090803

Description of problem:

When configuring power management for a host, Slot number is entered to identify the cisco ucs blade. When this blade number is passed to the fencing script, fencing would fail with the below error message.

Failed: Unable to obtain correct plug status or plug is not available

Instead the fencing script expects the Service Profile name of the ucs_blade and that need to be entered for fencing to work properly.

This RFE is to change label "Slot" to "Service Profile" on the GUI when cisco_ucs is selected as the fencing type so that users will not misunderstand and enter blade number which ends up in a failure for fencing.

How reproducible:

Always.

<snip>

Summary: the required parameter is misleadingly labeled 'Slot' in Power management configuration dialog. It should read 'Service profile'. The script works as expected when you use service profile name instead of slot number.

fence_cisco_ucs script prepends 'org-root/ls-' to the parameter given in 'Slot' field. If given a number, the script tries something like 'org-root/ls-4/power' but this fails and the script outputs 'Failed: Unable to obtain correct plug status or plug is not available'. This is misleading, because word 'plug' has no meaning to the end user in this context. It comes from /usr/share/fence/fencing.pyc which is byte-compiled python.

Service profiles (one for each blade) are named org-root/ls-<service-profile-name> . It it this service profile name the script expects, not a slot number.

In most places in UCS manager, things are referred to like sys/chassis-1/blade-3/... and the 'General' view on a server shows 'Slot ID: <number>', which adds to confusion in this case.
</snip>