This Readme contains information about NetIQ Cloud Manager 2.1.3 issues you might encounter. The Readme is divided into the following sections:
The following issues might be encountered during Cloud Manager installation:
The Cloud Manager Orchestration installation media does not include the RHEL monitoring packages.
If you want to monitor RHEL resources, we recommend that you download Ganglia 3.1.7 from the SourceForge Web site and install it on the resources to be monitored. Create a .conf file similar to one that exists on a SLES machine, editing the node name in the file so that the monitoring metrics display for the resource in the Orchestration Console.
If you choose to install NetIQ Cloud Manager and a PostgreSQL ORDBMS on the same SUSE Linux Enterprise Server 11 (SLES 11) machine, the NetIQ Cloud Manager YaST installation marks the postgresql-server package as a recommended install package and looks for this package on the local host. If an older version of Postgres (8.3.18-0.3.1 or earlier) is present on the machine, the installation proceeds normally. If the Cloud Manager 2.1.3 installation program detects a Postgres package newer than this, it cannot configure this newer version when it is installed on the same machine with Cloud Manager itself.
IMPORTANT:Any Postgres package version later than 8.3.18-0.3.1 fails when Cloud Manager 2.1.3 tries to configure it.
Workaround: If you want to use Postgres and Cloud Manager on the same machine, avoid using Postgres packages newer than version 8.3.18-0.3.1.
Use one of these approaches to avoid installing newer Postgres packages:
Install the supported Postgres package before you install Cloud Manager.
Install the supported package using the zypper command:
zypper in postgresql-server=8.3.18-0.3.1
NOTE:The SLES update service keeps older versions of the Postgres database package as well as the updated version.
In YaST, select the NetIQ Cloud Manager pattern, select the NetIQ Cloud Manager pattern and retain its associated default packages.
Run the Cloud Manager configuration program to configure Postgres.
Install the supported Postgres package after you install Cloud Manager.
In YaST, select the NetIQ Cloud Manager pattern, then deselect the preselected Postgres packages before you click .
Install the supported Postgres package using the zypper command.
zypper in postgresql-server=8.3.18-0.3.1
Run the Cloud Manager configuration program to configure Postgres.
If you do not install the Cloud Manager Monitoring Server package during the installation of the Cloud Manager Orchestration components, later attempts to set up the server for high availability by running the zos_server_ha_post_config.sh script fail.
Workaround: If you intend to use the Orchestration Server in a high availability environment, you must install the Cloud Manager Monitoring Server package with it.
For information about the Cloud Manager Monitoring installation pattern, see Cloud Manager Monitoring Server Pattern
in the NetIQ Cloud Manager 2.1.3 Installation Planning Guide.
For information about installing the Monitoring pattern in YaST, see Step 5 in the Installing the Orchestration Server to a SLES 11 Pacemaker Cluster Environment
procedure of the NetIQ Cloud Manager 2.1.3 Orchestration Server High Availability Configuration Guide.
For information about configuring Cloud Manager Orchestration Monitoring, see Configuring the Monitoring Server and Monitoring Agent
in the NetIQ Cloud Manager 2.1.3 Orchestration Installation Guide.
The following information is included in this section:
If your Cloud Manager 2.1.2 installation has been configured to enable SSL security for its LDAP connection but SSL is not configured for the connection to the web service (Jetty), the upgraded Cloud Manager Application Server throws a Java exception when you attempt to log in.
Workaround: Manually reconfigure the login credentials to accept your SSL selection.
At the Cloud Manager Application Server, open /etc/opt/netiq/cloudmanager/etc/com.novell.cm.backend.ldap.cfg and note the following values:
keystore.keystorePassword=<value> keystore.keyPasswords=<alias_value>=<pwd_value> ssl.keyalias=<value>
Open /etc/opt/netiq/cloudmanager/etc/com.novell.cm.ncss.connector.cfg and make the following attribute value substitutions from the values you noted in Step 1:
connector.keystore.password: Substitute the keystore.keystorePassword value.
connector.keystore.signing-key.alias: Substitute the ssl.keyalias value.
connector.keystore.signing-key.password: Substitute the <pwd_value> part of the keystore.keyPasswords value.
The following issues might be encountered with the Cloud Manager Application components:
A Cloud Manager user might see intermittent display problems in the Cloud Manager Web console interface where some tabs are not properly displayed.
If you encounter this problem, we recommend that you restart the Cloud Manager Application Server.
If you choose to edit a resource group in the Cloud Manager Application Console and if that resource group has a VMware resource pool affiliation, you cannot add hosts to that Cloud Manager resource group, even though the option is active in the dialog box.
The problem will be corrected in the next Cloud Manager release.
When you attempt to save more than one Cloud Manager .pdf report from a Firefox browser (version 15.0.1) while viewing the Cloud Manager Application Server Console, attempts to save more than one .pdf report fail.
Workaround: Log out of the console and log back in to save one report at a time, or use another browser, such as Microsoft Internet Explorer 9, to view and save multiple reports in .pdf format in the same session.
The following issues might be encountered with the Cloud Manager Orchestration components:
The following information is included in this section:
Beginning with the 2.1.2 release, NetIQ Cloud Manager deploys workloads managed by the VMware ESX hypervisor only into resource pools that have been configured on an associated cluster. This requires that the Cloud Manager administrator assign these VMware resource pools to NetIQ Cloud Manager resource groups.
The following information is included in this section:
In the Orchestration Console, when you perform a Move operation on a Citrix Xen VM that includes a VM snapshot, the move of the VM itself is performed, but its associated snapshots do not move with it. Those snapshot disk files remain in the source repository.
Currently, there is no workaround for this issue.
Deployed Windows 2003 VMs in a Citrix XenServer environment render a Service Control Manager error at login time as the workload is booting. Information from the Windows Event viewer leads to a PSOSysprep service that has failed to start.
At the fully deployed stage of the Windows workload lifecycle in Cloud Manager, the PSOSysprep service has already executed and is no longer needed. You can disregard the error.