Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Support for fence_ilo_ssh fencing agent
The fence_ilo_ssh fencing agent is a fence agent that connects to an iLO device. It logs into the device via ssh and reboots a specified outlet. For information on the parameters for the fence_ilo_ssh fencing agent, see the fence_ilo_ssh(8) man page.
1. What is the nature and description of the request?
An additional fencing agent based on ssh should be added to RHEV. Idea is that a generic command can be given for fencing. Thus e.g. ILO systems or blades can be fenced by connecting via ssh to the ILO itself avoiding IPMI (which is forbidden due to security reasons)
2. Why does the customer need this? (List the business requirements here)
As security forbids using IPMI, and single blades can only be fenced using the ILO, a generic ssh fencing daemon is needed to apply whatever command needed to power off/reboot the blade to the ILO via ssh.
Without fence_ssh no fencing in RHEV is possible, as the remaining fence_ipmi is not allowed from the security group.
The customer actually has a production risk at the moment already as the newly added systems can't be fenced,
so in order of any hardware failure, ha-flaged VMs cannot be restarted.
3. How would the customer like to achieve this? (List the functional requirements here)
Add a fence_ssh agent that is able to connect to whatever IP with Username/Password or Username/Key to a system (ILO) and run a given command.
The command should be configurable as a fencing parameter to support as many different ILO types as possible.
4. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
Configure the fence_ssh
Run the fencing
Check if the host was powered off /reset / etc. according to the command that has been run.
5. Is there already an existing RFE upstream or in Red Hat Bugzilla?
Not that I am aware off.
6. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
RHEV 3.x
7. Is the sales team involved in this request and do they have any additional input?
No.
8. List any affected packages or components.
RHEV / RHEV-M
9. Would the customer be able to assist in testing this functionality if implemented?
Yes.
Created attachment 912708[details]
Proposed fencing library
Together with proposed fence agent, you can test functionality.
fence_ilo_mp -l user -p password -a ilo-node --method=cycle -o reboot
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://rhn.redhat.com/errata/RHBA-2015-1350.html