HP Serviceguard Version A.11.17 Release Notes, March 2006 (revised)

Serviceguard Version A.11.17 Release Notes
Fixed in This Version
Chapter 142
JAGaf42015 (SR8606381803): what(1m) does not show
any output for package control scripts
What was the problem? The what (1m) command will not display any
information about Serviceguard package control scripts.
What was the resolution? Correct the format in the package control
script.
JAGaf41616 (SR8606381403): cmgetconf didn't write
access control policies after conversion
What was the problem? The cmgetconf command fails to report the
converted access control policies after rolling upgrade.
What was the resolution? The command will check the Serviceguard
version to verify if access control policies need to be processed.
JAGaf40772 (SR8606380547): package script imports
VxVM dg on multiple nodes at the same time
What was the problem? For a particular package, if that package uses
VxVM disk groups then the VxVM disk groups might get activated on
multiple nodes, leading to possible data corruption. If CVM disk groups
and/or LVM volume groups are used without VxVM disk groups then
those packages are not affected.
his problem can happen if that package fails to halt on one node, leaving
the VxVM disk group(s) active and then a user attempts to start the
package on another node without first having cleaned up the VxVM disk
groups that were left active on the node where the package halt failed.
This problem could also occur if the user had manually imported a VxVM
disk group for maintenance reasons on one node, and then accidentally
started the package using that VxVM disk group without first deporting
the VxVM disk group.
What was the resolution? The package control script template has been
corrected so that it will exit after detecting a disk group is possibly active
on another node rather than removing hostid protection from a VxVM
disk group, and mounting/unmounting it.