Cloud Manager 2.3 Patch 2 (NCM_2.3.0_Patch2.zip) is a cumulative patch: all of the files needed to update the Cloud Manager Application Server 2.3 and the Cloud Manager Orchestration Server 3.3 (including Patch 1 and Patch 2) are included.
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.3 NetIQ Documentation page.
The following bugs are fixed when you apply the files included Cloud Manager 2.3 Patch 1:
Bug 876774: cmMobile: Unable to create workload template - error: Missing Selection.
Adjustments for null pointer exception in IdentityContextManager.
Adjustments to ForceWorkflowCompletionCommand command to attempt to clean up Business Service Requests and Change Requests that have no workflow.
Enhanced workflow-related logging.
Bug 861085 - [FTF] NCM 2.2.0/2.2.2 Imported machine adding new NIC fails - Error No root disk found.
Fixed an issue with datastore search: Searching from the root directory rather than the subdirectory, which caused provisioning jobs to take a long time to complete.
Fixed an issue with detecting a virtual machine’s (VM’s) VNC port configuration: Occasionally, vSphere reflected an empty string "" as the value, causing a failure when casting an empty string to an integer. The fix added a check to make sure there is a value in the extra configuration port setting for a VM before trying to cast it to an integer.
Formerly, the contents of the .../config, .../console, and .../plugins directories located on the Cloud Manager Application Server were accessible with a web browser, making those folder listings visible to users. This potential security issue was resolved by making those folders forbidden to browsing.
The following bugs are fixed when you apply the files included Cloud Manager 2.3 Patch 2:
SR10907978361 - In some configured vSphere environments, customers would change a workload on the ESX server and that change would not be replicated in the vSphere Updater job in the Cloud Manager Orchestration Server. This could be manifest with errors such as VM Tools Not Running. The updater has been modified to function correctly after applying the Orchestration Server Patch.
SR10919554851 - Formerly, email notifications were being sent only to the business service requester. With this patch, a Cloud Administrator can add a specific property to the /opt/netiq/cloudmanager/etc/system.properties file, any user with specified permission(s) on the business service receives an email notification.
For further implementation details, see Enabling Email Notifications for Users with Specific Permissions in this document.
SR10920711341 - A user (such as a Business Group Owner or Business Group Viewer) can now search for values in the Hostname field on the deployed workloads list.
SR10918270071 - If you have multiple blocks in your IPAM with the same NCMNetworkID and then import a VM using that network into Cloud Manager, the VM could end up in a state where it has no association to its IPAM address, which would cause it to fetch a new IP address on a change request. The product now detects duplicate NCMNetworkID values and cleans them up.
SR10918026811 - Formerly, running the Business Service Cost Details report without a start date parameter (the default) could stall the report builder. The report can now be generated without a start date.
Bug 901327 - Formerly, if you were to select a deployed business service and then select Change, the Hostname field was not included in the list of workloads. The hostname field has now been added on the workload list for the Change operation.
Ensure that the following prerequisites are met before you install this patch:
Cloud Manager Orchestration Server 3.3 is installed, and is up and running.
Extract the cmos.zip file from Cloud Manager 2.3 Patch 2 (NCM_2.3.0_Patch2.zip) and copy the following files to an accessible directory on the Cloud Manager Orchestration Server:
libvsphere.pylib (fixes made in Patch 1)
vmprep.sar (fixes made in Patch 1)
vi-client.jar (fixes made in Patch 2)
vsphere.sar (fixes made in Patch 2)
NOTE:If you have never applied a patch to the Cloud Manager Orchestration Server 3.3, you must apply all of the files listed above. If you previously applied Patch 1, you must apply only the files for Patch 2.
NOTE:If you see an incorrect FQDN on a workload after applying the files in this patch, you might need to rediscover the VMs.
Copy libvsphere.pylib to the following location:
/opt/novell/zenworks/zos/server/components/pylib/libvsphere.pylib
In the Explorer Tree of the Orchestration Server console, expand the Public JDL Libraries container, right-click the libvsphere object, then select Undeploy.
Right-click the Public JDL Libraries container, select Deploy, then browse to the location of the new library (see Step 1 above):
/opt/novell/zenworks/zos/server/components/pylib/libvsphere.pylib
This redeploys the libvsphere library.
Copy vmprep.sar to the following location:
/opt/novell/zenworks/zos/server/components/jobs/vmprep.sar
In the Explorer Tree of the Orchestration Server console, expand the Jobs container and then the all container, right-click the vmprep object, then select Undeploy.
Right-click the all container, select Deploy, then browse to the location of the new library (see Step 1 above):
/opt/novell/zenworks/zos/server/components/jobs/vmprep.sar
This redeploys the vmprep job.
Copy vi-client.jar to the following location:
/var/opt/novell/zenworks/zos/server/store/deployed/vsphere.sar-<jobid>/vSphereUpdate.job/vi-client.jar
Restart the vSphereUpdate scheduled job.
In the Scheduler view of the Orchestration Server console, locate and select the vSphereUpdate scheduled job.
On the Job Arguments page of the Job details section of the view, locate the mode field, ensure that the accompanying Lock check box is deselected, and type stop in the field.
In the console toolbar, click the Save icon, in the Scheduler view click Run Now, then monitor the job progress.
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.
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.
The netiq-cloudmanager-2.3.0-183.noarch.rpm file found in NCM_2.3.0_Patch2.zip is specifically for the Cloud Manager Application Server 2.3. The RPM is an installer program that applies cumulative patch files (that is, all of the updated .jar files for every patch that has been released to date) to the Cloud Manager Application Server 2.3.
For your information, the files included in the RPM include the following:
common-79.*.jar
Fixes a Cloud Manager Mobile bug.
cm-core-79.*.jar
Includes adjustments for null pointer exception in IdentityContextManager, for forceworkflow, and increased logging capabilities for workflow.
Includes adjustments to allow sending email notifications to users with specified permissions.
Detects and fixes a missing IPAM configuration when a workload is synchronized.
Includes a Karaf command that attempts to recover IPAM configuration data for all workloads whose IPAM configuration information has been cleared because more than one entry existed in IPAM for one network.
Run the following command from the Karaf shell:
cm:recover-ipam-releasedata
You can add the -b business service ID option to the command if you want to recover IPAM configuration data for all workloads in a business service. For more options for this command, use the --help option.
external-79.*.jar
Fixes a Cloud Manager Mobile bug.
Allows filter/search in the workloads list to identify workloads based on the computer name.
persistence-79.*.jar
Fixes a Cloud Manager Mobile bug.
Allows filter/search in the workloads list to identify workloads based on the computer name.
cm-task-core-79.*.jar
Includes adjustments for null pointer exception in IdentityContextManager, for forceworkflow, and increased logging capabilities for workflow.
cloudmanager-2.3.*.war
Allows filter/search in the workloads list to identify workloads based on the computer name.
pso-service-79.0.*.jar
Includes a Karaf command that surfaces the timings of calls to the REST interface of the Cloud Manager Orchestration Server.
The following command turns on a log trace for the elapsed time of all REST calls to the server:
karaf> log:set TRACE com.novell.cm.psoservice.impl
The following command resets the log level to default so these timing messages no longer appear in the log:
karaf> log:set INFO com.novell.cm.psoservice.impl
This section includes the following information:
Ensure that the following prerequisites are met before you run the RPM:
Cloud Manager Application Server 2.3 is installed, and is up and running.
Extract the netiq-cloudmanager-2.3.0-183.noarch.rpm file from the patch (NCM_2.3.0_Patch2.zip) and copy it to an accessible directory on the Cloud Manager Application Server.
For example: /tmp/ncm2.3_patch/netiq-cloudmanager-2.3.0-183.noarch.rpm
After you have copied the patch file to the server, use the following steps to install the file:
From the location where you copied netiq-cloudmanager-2.3.0-183.noarch.rpm, run the following command:
rpm -Uvh --nodeps netiq-cloudmanager-2.3.0-183.noarch.rpm
Run the Cloud Manager configuration program from the following location:
/opt/netiq/cloudmanager/configurator/config
Choose to run an upgrade for the Cloud Manager Server.
Verify that the netiq-cloudmanager-2.3.0-183.noarch.rpm file is installed.
Log in to the Cloud Manager Web Console.
In the Web Console, click Help > About.
In the About box, verify the following:
Server version is 2.3.0 and build number is 79.0.181
Web UI version is 2.3.0 dated 11/17/14
You can control the individuals who can receive email notification when a business service is deployed or a change request has completed if you add the ncm.bs.deploy.perms property to the /opt/netiq/cloudmanager/etc/system.properties file.
As you add this new property, you also need to add the permissions to be honored on the business service. Any user with those permissions will receive the email notifications. For example, if you wanted a user with SYSTEM_SUPPORT permission or MODIFY_BS or VIEW_BS permission to receive emails when the business service is being deployed or changed, you would modify the /opt/netiq/cloudmanager/etc/system.properties file like this:
... ... ncm.bs.deploy.perms=SYSTEM_SUPPORT,MODIFY_BS,VIEW_BS ... ...
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.
THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT ARE FURNISHED UNDER AND ARE SUBJECT TO THE TERMS OF A LICENSE AGREEMENT OR A NON-DISCLOSURE AGREEMENT. EXCEPT AS EXPRESSLY SET FORTH IN SUCH LICENSE AGREEMENT OR NON-DISCLOSURE AGREEMENT, NETIQ CORPORATION PROVIDES THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. SOME STATES DO NOT ALLOW DISCLAIMERS OF EXPRESS OR IMPLIED WARRANTIES IN CERTAIN TRANSACTIONS; THEREFORE, THIS STATEMENT MAY NOT APPLY TO YOU.
For purposes of clarity, any module, adapter or other similar material (“Module”) is licensed under the terms and conditions of the End User License Agreement for the applicable version of the NetIQ product or software to which it relates or interoperates with, and by accessing, copying or using a Module you agree to be bound by such terms. If you do not agree to the terms of the End User License Agreement you are not authorized to use, access or copy a Module and you must destroy all copies of the Module and contact NetIQ for further instructions.
This document and the software described in this document may not be lent, sold, or given away without the prior written permission of NetIQ Corporation, except as otherwise permitted by law. Except as expressly set forth in such license agreement or non-disclosure agreement, no part of this document or the software described in this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, or otherwise, without the prior written consent of NetIQ Corporation. Some companies, names, and data in this document are used for illustration purposes and may not represent real companies, individuals, or data.
This document could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein. These changes may be incorporated in new editions of this document. NetIQ Corporation may make improvements in or changes to the software described in this document at any time.
U.S. Government Restricted Rights: If the software and documentation are being acquired by or on behalf of the U.S. Government or by a U.S. Government prime contractor or subcontractor (at any tier), in accordance with 48 C.F.R. 227.7202-4 (for Department of Defense (DOD) acquisitions) and 48 C.F.R. 2.101 and 12.212 (for non-DOD acquisitions), the government's rights in the software and documentation, including its rights to use, modify, reproduce, release, perform, display or disclose the software or documentation, will be subject in all respects to the commercial license rights and restrictions provided in the license agreement.
© 2014 NetIQ Corporation. All Rights Reserved.
For information about NetIQ trademarks, see http://www.netiq.com/company/legal/.