RHBA-2009:1516: bug-fix update
21
Consequent to these two changes, the first node to fence removes the other node's key from the
device or devices. The second node, now not registered with the device, is not able to fence the first.
This allows fence_scsi to work in a 2-node cluster. (
BZ#520823
115
)
All cman users should install this updated package, which fixes this bug and enables users to use
fence_scsi in a 2-node environment.
1.19.2. RHBA-2009:1516: bug-fix update
Note
This update has already been released (prior to the GA of this release) as errata
RHBA-2009:1516
116
Updated cman packages that fix a bug are now available.
The Cluster Manager (cman) utility provides user-level services for managing a Linux cluster.
This update applies the following bug fix:
Add support for power cycle command to fence_ipmi, which doesn't shut down the BMC controller.
Old behavior is still the default, so nothing changes without a configuration change. Now there is a
new method option that can have the value "cycle", which uses the ipmi power cycle command.
Example of usage:...
<fencedevices> <fencedevice agent="fence_ipmilan_new" ipaddr="1.2.3.4" login="root"
name="ipmifd1" passwd="password" method="cycle" /> ...
Users are advised to upgrade to these updated cman packages, which resolve this issue.
1.19.3. RHBA-2009:1598: bug fix update
Note
This update has already been released (prior to the GA of this release) as errata
RHBA-2009:1598
117
Updated cman packages that resolve several issues are now available.
[Updated 4 Jan 2009] This update provides improved descriptions of both bug fixes included in this
advisory, and especially the description for bug 529712. The packages included in this revised update
have not been changed in any way from those included in the original advisory.
The Cluster Manager (cman) utility provides user-level services for managing a Linux cluster.
These updated cman packages provide fixes for the following bugs:
* when using device-mapper-multipath devices, registrations were only sent to the active path,
which meant that, in the event of path failure, the node would be unable to access the device via the
115
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=520823
Summary of Contents for ENTERPRISE LINUX 5.5 - S 2010
Page 10: ...x ...
Page 308: ...298 ...
Page 310: ...300 ...
Page 468: ...458 ...
Page 470: ...460 ...