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

Serviceguard Version A.11.17 Release Notes
Fixed in This Version
Chapter 1 33
What was the resolution? Ignore the status update message.
JAGaf69163 (SR8606409265): mistake with ACP causes
cmcld to abort on all nodes during cmapplyconf
What was the problem? Invalid data can be specified in the USER_NAME
field for the access control policies in the cluster ascii file and a
cmapplyconf will complete without error. When a cmapplyconf is
re-executed to correct this, and if the cluster is running, cmcld will
abort, resulting in a node TOC. The following message will be logged in
syslog when an invalid username is applied:
Jul 12 11:34:08 sly cmcld: ERROR:
Invalid user name in RBA Privilege lookup
Messages like the following would be logged in syslog when the invalid
username was corrected:
Jul 12 11:35:06 sly cmcld:
cdb_db_handle_lookup - More than one found
Jul 12 11:35:06 sly cmcld: CDB Prepare -
Unable to delete /acps/sly/*, object does not exist
Jul 12 11:35:06 sly cmcld: CDB Prepare -
Unable to perform configuration operation 2. Return
value is 22.
Jul 12 11:35:06 sly cmcld: Aborting:
cdb/cdb_db_server.c 1937 (Failed to roll back config
change
Jul 12 11:35:06 sly cmcld:
cdb_db_handle_lookup - More than one found
Jul 12 11:35:10 sly cmclconfd[6699]: The Serviceguard
daemon,
/usr/lbin/cmcld[6700], died upon receiving signal
number 6.
Data from the USER_NAME field is not validated when cmapplyconf is
run, although an error is reported in syslog by cmcld if the USER_NAME
is invalid. When an invalid username is corrected and cmapplyconf
re-executed cmcld aborts due to the invalid data in the CDB.
What was the resolution? Appropriate checks are now added to be
consistent with the checking for CLUSTER_NAME, PACKAGE_NAME, etc.