NetIQ Cloud Manager 2.4 Patch 1 Release Notes

June 2015

This file contains information about NetIQ Cloud Manager 2.4 Patch 1. The Application Server component of Cloud Manager (specifically, Cloud Manager Application Server 2.41) and the Orchestration Server component of Cloud Manager (specifically, Cloud Manager Orchestration Server 3.4) are affected by this patch.

NetIQ Corporation strives to ensure our products provide quality solutions for your enterprise software needs. If you need further assistance with any issue, please contact Technical Support.

The documentation for this product is available on the NetIQ website in HTML and PDF formats. If you have suggestions for documentation improvements, click Comment on this topic at the bottom of any page in the HTML version of the documentation posted at the Cloud Manager 2.4 NetIQ Documentation web page.

1.0 Issues Fixed in This Patch

The following bugs have been fixed in Cloud Manager 2.4 Patch 1:

  • 932777: Issue with IPAM communication during the imports. Previously, during import and workload synchronization, timeout issues and excessive logging occurred in very large networks when Cloud Manager checked IP addresses of workloads.

    Cloud Manager now searches the NIXU IPAM host only to check if a specified IP is registered in the network. Excessive logging by the NIXU API client is now disabled by default. To enable NIXU API logging, you can enable the apilogging option in the /opt/netiq/cloudmanager/etc/cloudmanager-ipam-nixu.cfg file:

    apilogging=true
    
  • 931391: NCM 2.4 zone in NCM offline. If a Zone is enabled and shows an Offline state in Cloud Manager, disable the zone then re-enable it. This resets the Online/Offline function.

  • 929767: Domain adding does not work in NCM 2.4. Previously, information about the Domain Administrator User ID and Domain information was not applied during provisioning, and it had to be entered again during the approval. This issue is resolved.

  • 929410: Adding a NIC or changing RAM/CPU intermittently fails to apply the changes. The timing of events was modified to prevent the conditions that caused the failure.

  • 928696: Business Service Owner ID issue for bulk import. Previously, when you imported multiple workloads to a new business service, the initial workload validation of the business service owner succeeded, but subsequent workload validations of the user reported the wrong ID. This issue is resolved.

  • 924329: Cloud Manager 2.4 Translation issues. Previously, several translation issues caused text to run off the page or to be misaligned. These issues are resolved.

  • Time display of events is not consistent and should match the local settings. The time format is now displayed consistently across the UI. The time will not be modified to display time for the local time zone.

  • Either 24 hour or AM/PM, but not 24 hour in the events and 12 hours without AM/PM in the event list. The time format is now displayed consistently across the UI.

  • Firefox is not allowing multiple entries for DNS Servers. This issue is resolved.

  • Display the workload ID in the Workload Detail view. This issue is resolved.

  • Hosts list will not load if a zone is offline. This issue is resolved.

  • Sponsor cannot deny a request. This issue is resolved.

  • When selecting View a Template from an Organization or Business Group, it shows retrieving data, but nothing happens. This issue is resolved.

2.0 Files Included in This Patch

The following files are included in Cloud Manager 2.4 Patch 1 (NCM_2.4.0_Patch1.zip):

  • cmos.zip (for the Orchestration Server), which includes these files:

    • vi-client.jar

    • vsphere.jdl

    • vsphere.sar

  • netiq-cloudmanager-2.4.0-125.noarch.rpm (for the Application Server)

3.0 Applying the Orchestration Server Patch

3.1 Patch Installation Prerequisites

Ensure that the following prerequisites are met before you install this patch:

  • Cloud Manager Orchestration Server 3.4 is installed, and is up and running.

  • Extract the files from cmos.zip (located inside the NCM_2.4.0_Patch1.zip patch file) and copy to an accessible directory on the Cloud Manager Orchestration Server.

3.2 Installing the Orchestration Server Patch Files

NOTE:If you see an incorrect FQDN on a workload after applying the files in this patch, you might need to rediscover the VMs.

Applying the vi-client.jar Patch File

To apply the vi-client.jar patch file to the Orchestration Server:

  1. Copy vi-client.jar to the following location:

    /var/opt/novell/zenworks/zos/server/store/deployed/vsphere.sar-<jobid>/vSphereUpdate.job/vi-client.jar

  2. Restart the vSphereUpdate scheduled job.

    1. In the Scheduler view of the Orchestration Server console, locate and select the vSphereUpdate scheduled job.

    2. On the Job Arguments page of the Job details section of the view, locate the mode field, deselect its Lock check box, and type stop in the field.

    3. In the console toolbar, click Save, then in the Scheduler view, click Run Now. Monitor the job progress.

    4. When the Job status shows success, delete the stop argument you previously entered in the mode field at Step 2.b, then repeat Step 2.c.

      This step ensures that the new vi-client.jar library you applied to the Orchestration Server is transferred to the Orchestration Agent running the vSphereUpdate job. The new library fixes the vSphere updater on the agent.

Applying the vsphere.jdl Patch File

To apply the vsphere.jdl patch file to the Orchestration Server:

  1. Open the vsphere.jdl file in a text editor, and copy its contents to the clipboard.

  2. In the Explorer Tree of the Orchestration Server console, expand the Jobs container, and expand the provisionAdapters group container. Select the vsphere job.

  3. Choose the JDL Editor tab for the vsphere job, delete all the contents in the editor space, and paste the contents from the new vsphere.jdl from the clipboard that you copied in Step 1.

  4. In the console toolbar, click Save.

Applying the vsphere.sar Patch File

To apply the vsphere.sar patch file to the Orchestration Server:

  1. Copy vsphere.sar to the following location:

    /opt/novell/zenworks/zos/server/components/jobs/vsphere.sar

    Copying the file ensures that the patched vi-client.jar is included in the vsphere job if it is ever re-deployed.

4.0 Applying the Application Server Patch

4.1 Patch Installation Prerequisites

Ensure that the following prerequisites are met before you install this patch:

  • Cloud Manager Application Server 2.4 is installed, and is up and running.

  • Extract the netiq-cloudmanager-2.4.0-125.noarch.rpm file from the patch (NCM_2.4.0_Patch1.zip) and copy it to an accessible directory on the Cloud Manager Application Server.

    For example: /tmp/ncm2.4_patch/netiq-cloudmanager-2.4.0-125.noarch.rpm

4.2 Installing the Application Server Patch

After you have copied the patch file to the server, use the following steps to install the file:

  1. From the location where you copied netiq-cloudmanager-2.4.0-125.noarch.rpm, run the following command:

    rpm -Uvh --nodeps netiq-cloudmanager-2.4.0-125.noarch.rpm

  2. Run the Cloud Manager configuration program from the following location:

    /opt/netiq/cloudmanager/configurator/config

  3. Choose to run an upgrade for the Cloud Manager Server.

  4. Verify that the netiq-cloudmanager-2.4.0-125.noarch.rpm file is installed.

    1. Log in to the Cloud Manager Web Console.

    2. In the Web Console, click Help > About.

    3. In the About box, verify the following:

      • Server version is 2.4.0 and build number is 80.0.341

      • Web UI version is 2.4.0 dated 06/04/2015

5.0 Contact Information

Our goal is to provide documentation that meets your needs. If you have suggestions for improvements, please email Documentation-Feedback@netiq.com. We value your input and look forward to hearing from you.

For detailed contact information, see the Support Contact Information website.

For general corporate and product information, see the NetIQ Corporate website.

For interactive conversations with your peers and NetIQ experts, become an active member of our community. The NetIQ online community provides product information, useful links to helpful resources, blogs, and social media channels.