Bug 1209957
Summary: | iLO2 no longer works under power fencing devices, ipmilan required instead | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Robert McSwain <rmcswain> |
Component: | ovirt-engine | Assignee: | Eli Mesika <emesika> |
Status: | CLOSED ERRATA | QA Contact: | Petr Matyáš <pmatyas> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.4.0 | CC: | adevolder, amureini, bazulay, emesika, juwu, kstrickl, lsurette, mgoldboi, pstehlik, rbalakri, Rhev-m-bugs, rmcswain, yeylon, ykaul, ylavi |
Target Milestone: | ovirt-3.6.0-rc | Flags: | mgoldboi:
Triaged+
|
Target Release: | 3.6.0 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Previously, fence agents accepted boolean agent flags as secure or lanplus (ex: lanplus, lanplus=1, or lanplus=true). The options became unsupported, and caused hosts with those fence agents types to stop functioning. With this update, the fencing options for any existing hosts will have the new format. Any implicitly added options will also have the new format. For existing hosts, the fence agents work as normal after the package is updated. If the options field was defined as an encrypted field, redefine the options field manually to align to the new format. For new hosts, the new format (i.e <key>=<value>) should be defined in the options field.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2016-03-09 21:02:12 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Robert McSwain
2015-04-08 14:05:52 UTC
First we have to understand why the iLO2 stopped working please attach engine log vdsm log of the host that was used to perform the fencing action It would be great if you could provide those for both 3.3 and 3.4 so we can see what was changed, but if you can't , the logs with failing 3.4 calls will be OK as well ovirt-3.6.0-3 release 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-0376.html |