HP WBEM Services Version A.02.07 Release Notes, March 2009

HP WBEM Services is not installed appropriately on systems that use NIS
• What is the problem? While installing HP WBEM Services, the configure phase creates the
cimsrvr user and group in the passwd(4) and group(4) files. But when you upgrade
to HP WBEM Services, as part of a custom bundle, on a system that has NIS configured, and
the custom bundle requires a restart, the configure phase is run before the NIS services are
up and running. This can cause user and group IDs to be created in the passwd(4) and
group(4) files that are already present in the NIS database.
This issue can also occur on systems that use other services, such as LDAP for user and
group management, and where those services are not available immediately after a system
is restarted.
IMPORTANT: This issue is applicable only for HP WBEM Services A.02.07 and later versions.
What is the workaround? On systems that have NIS, LDAP or other user and group
management services configured, install the HP WBEM Services A.02.07 upgrade on its own
or as part of a custom bundle that does not contain updates that require a restart.
This problem does not affect new installations where the cimsrvr user and group is present
before NIS is configured; or minor upgrades of HP WBEM Services A.02.07 where the
cimsrvr user and group is present from an earlier HP WBEM Services A.02.07 installation.
Message while cold-installing HP WBEM Services A.02.07.04
• What is the problem? While cold-installing HP WBEM Services, the SSL certificates may be
generated with short host names. These certificates cannot be used by the WBEM Service
clients. The following message is logged in the swagent.log file:
Note: Cannot find the fully-qualified domain name (FQDN) for this
system, SSL certificates for WBEM Services are created with the
short hostname.
Correct this either by editing the /etc/hosts file or by making the
appropriate DNS registration. If not corrected, the created
certificates may not be acceptable to the WBEMService clients that
expect a FQDN in the common name field of the SSL certificate.
After the hostname(FQDN) is configured, run
/opt/wbem/sbin/gen_wbem_certs to create SSL certificates for
WBEMServices. The existing certificates /etc/opt/hp/sslshare/cert.pem
and /etc/opt/hp/sslshare/file.pem will be moved to
/etc/opt/hp/sslshare/cert.pem.bak and
/etc/opt/hp/sslshare/file.pem.bak respectively.
• What is the workaround? After configuring the host name, run the /opt/wbem/sbin/
gen_wbem_certs utility to create SSL certificates for HP WBEM Services.
Failure to configure WBEM-CORE fileset (Updating from A.02.00.08 and earlier to A.02.05 and
later)
• What is the problem? Use of the usePAMAuthentication configuration option will result
in failure to configure the WBEM-CORE fileset during an update of the WBEM Services.
The usePAMAuthentication configuration option has been obsoleted and is no longer
supported.
• What is the workaround or available patch? You must do the following:
1. Before updating the WBEM Services, check if the usePAMAuthentication configuration
option is present in the following WBEM configuration files:
/var/opt/wbem/cimserver_current.conf
Patches and Fixes in this Version 25