Hide Forgot
1. Proposed title of this feature request Add Fencing of Ilo3/4 via ssh fencing to RHEV-M 3. What is the nature and description of the request? As RHEL 6.7 and RHEL 7.1 include ssh based fencing of ILO3/4 devices, please add this agent to RHEV as well. 4. Why does the customer need this? (List the business requirements here) The customer is not allowed to use ipmilan in its premises, so he needs to use ssh-based fencing method for ILO devices. 5. How would the customer like to achieve this? (List the functional requirements here) Add the newly added fence agent to RHEV-M as a configurable agent. (See BZ #1121122 and BZ #1111482) 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. Configure fencing with ILO3/4 ssh-agent and check that a manual fencing is possible 7. Is there already an existing RFE upstream or in Red Hat Bugzilla? No 8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? RHEL 6.7 would be acceptable as the fence agent is added with RHEL 6.7 to RHEL 6. 9. Is the sales team involved in this request and do they have any additional input? No 10. List any affected packages or components. RHEV-M ovirt-engine-backend 11. Would the customer be able to assist in testing this functionality if implemented? Yes.
As the fence agent is now available within RHEL 6.7, can we go ahead and add that agent to RHEV as well?
*** Bug 1314334 has been marked as a duplicate of this bug. ***
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Verified on ovirt-engine-4.0.0-0.0.master.20160405041403.git4ffd5a4.el7.centos.noarch
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/RHEA-2016-1743.html