Known limitations for IBM Workload Deployer Version 3.1 Clean the browser cache after appliance firmware update Problem: Outdated static content such as CSS, JavaScripts and images remain in the browser cache after an appliance firmware update. This causes the user interface menu and panels to display outdated information within the first 30 minutes after the update. Resolution: Clean up the browser cache when the firmware update is complete or wait 30 minutes before accessing information with the user interface. Deployed IBM PowerVM virtual systems display incorrect CPU utilization Problem: The CPU utilization displayed in the Workload Deployer Virtual Application Console for deployed PowerVM virtual systems shows incorrect statistics. For example, CPU utilization displays at 99 percent, when the actual usage is much lower, such as 8 percent. Resolution:Accurate CPU utilization statistics for PowerVM virtual systems deployed from topology patterns are not available from the Virtual Application Console. Using a Secure Shell (SSH) session to the PowerVM virtual machine, you can use the AIX command "topas" to view the actual CPU utilization. Error occurs when an IBM WebSphere Application Server Hypervisor Edition image is deployed Problem: When a WebSphere Application Server Hypervisor Edition, Version 8.0.0.1 image is deployed on Workload Deployer an error displays in the Hypervisor Edition startup logs, specifically in the remote_std_err.log. The error indicates "WVER0015E: An exception occurred while processing version information". Resolution: The error does not create a problem with the integrity of the deployment. Ignore the error message and continue to use the Version 8.0.0.1 deployment. Monitoring agent name is displayed inconsistently Problem: When viewing information that is associated with the Monitoring Agent for IBM Workload Deployer using the IBM Tivoli Monitoring user interface in languages other than English, the name of this agent is displayed inconsistently. In non-English locales, the name of the agent is displayed as "Workload Agent". Resolution: The names used to identify the agent all refer to the Monitoring Agent for IBM Workload Deployer. While the names are used inconsistently across locales, they all refer to the same agent. Stopping a point cell causes the application placement controller to stall Problem: The application placement controller might remain in a holding state for 20 minutes when you stop a point cell in an environment in which multi-cell performance management is configured. This problem exists when you are using IBM WebSphere Application Server Hypervisor Edition Intelligent Management Pack Version 7.0.0.2 with WebSphere Application Server Hypervisor Edition Version 7.0.0.19 or Version 8.0.0.1. Stopping a cell requires you to stop each virtual machine individually. During this process, however, the application placement controller is alerted that a particular node is being stopped and attempts to take corrective action without recognizing that the entire cell is being stopped. For example, the application placement controller might attempt to meet the dynamic cluster criteria, such as maintaining the minimum number of instances. As a result, the application placement controller stalls for 20 minutes. Resolution: To stop a point cell without the application placement controller stalling for 20 minutes, complete the following steps: 1. Place the application placement controller out of elasticity mode if it is set. 2. In the point cell that is being stopped, set all of the dynamic clusters to manual mode. 3. Stop the point cell. 4. Enable elasticity mode if it was disabled in step 1. Time zone field on the Auditing page of the user interface has no effect on selection criteria for downloading audit event recordsProblem: The time zone selections on the System > Auditing page, in the section Download filtered data, are inactive. When you specify a date and time range for downloading your audit data, those date and time values are automatically defined with the time zone of the appliance. You cannot refine your date and time selections with a different time zone. Additionally, be aware that every audit event record that you download has a UTC timestamp. Resolution: No workaround is available. Base image update is a prerequisite for V3.1 virtual application instances Problem: Virtual machines that are associated with new virtual application deployments display an ERROR status after starting. In addition, logs are not available from the Virtual Application Console and Secure Shell (SSH) access does not work. This error occurs because Workload Deployer 3.1.0.0 includes a new version of the Foundation Pattern type (2.0.0.0), that requires the latest version of the base image for virtual applications. This upgrade affects all new virtual application deployments because the Foundation Pattern type contains common plug-ins that are included in all new virtual application deployments. Resolution:You must upgrade to the latest base image to resolve the problem. To upgrade the base image, follow these steps: 1. Import the latest base image into the Workload Deployer catalog. From the menu, click Cloud > Virtual Images and select the New icon (+) in the Virtual Images palette. 2. Set the latest base image as the default. From the menu, click Cloud > Default Deploy Settings. The Settings for Default Deploy palette displays. Click Change and select the base image that you imported. Click Update to save the change. Scale in does not work for ELB instances when elbMgmt is not the agent master Problem: The scale in feature does not work for ELB instances when elbMgmt is not the agent master. When the elbMgmt is the agent master, you can scale in ELB instances. Resolution: If you must scale in ELB instances and the feature does not work, call IBM Support for assistance. Web Application Pattern V1.0.0.x applications that use a routing policy cannot be deployed with ELB service Fix Pack 2 Problem: Applications that use the Web Application Pattern V1.0.0.x and a routing policy cannot deploy to the ELB Proxy Service Version 2. Resolution: Call IBM Support. Email notifications do not identify appliance sending the emailProblem: Specific appliance information is not included in email notifications reporting IP addresses and deployment status, such as started, completed, and failed. Currently, email notifications are not identifying the appliance for which the processes and IP address are being recorded. Therefore, the user does not know which appliance the information is associated with. Also, the email notifications are specifying that IP addresses are inactive, but these addresses are in use and can be pinged in the network. Resolution: No workaround available. Failed deployments cannot be removed Problem: When users deploy virtual system patterns using an environment profile that has the "Pattern Deployer" option for IP addresses, the deploy fails if the hypervisor is running out of its capacity, such as storage, memory, and CPU. In addition, the IP addresses that the user allocated are added to the IP group, but are still inactive. Deleting these inactive IP addresses causes problems cleaning the failed virtual systems. Resolution: Delete the failed virtual systems with ignore errors before removing the IP addresses from its IP group. Deployments fail when hypervisor communications hang Problem: A deployment of virtual systems, applications or appliances fails with the error message "Not all cloud resources could be reserved" when the hypervisor communication hangs. Resolution: If this message displays and the cloud has adequate resources for hosting the deployment, ensure that the hypervisors are still running and that the appliance can communicate with them. IBM HTTP Server nodes not routing through the on demand router (ODR) Problem: For virtual systems that include IBM HTTP Server and ODR, the IBM HTTP Server does not route through the ODR as it should. Resolution: You must restart the IBM HTTP server after deployment. Virtual images fail to transfer to the hypervisor Problem: During deployment of virtual systems, applications or appliances, transfer of virtual images to hypervisors fails without any details in the error message. Resolution: The image transfer is retried by IBM Workload Deployer. Misleading message when starting a virtual application that uses a virtual hostname that is used by elastic load balancer (ELB) Problem: When a virtual application that uses a virtual hostname or routing policy that is already configured in ELB proxy service is deployed, a misleading error message is displayed. The following is an example of the type of message you see: CWZKS1053E:createServiceelbServicePlaceholder/2.0.0.0_com.ibm.elbservice.placeholder.ELBPlaceholderServiceProvisioner error. Ensure service is started. Because the ELB proxy service is already started, this message is misleading. The message should indicate that the combination of virtual hostname and context root is already in use. Resolution: Call IBM Support. isRequestedSessionIdValid and isNew methods return incorrectly when using the caching service Problem: The isRequestedSessionIdValid method returns true and the isNew method returns false incorrectly after a session is explicitly invalidated followed by a getSession(false) call to the web application. Resolution: Ensure that the appropriate WebSphere eXtreme Scale fixes are applied. Interim Fix 7.1.0.3 ensures that the 7.1.0.3 client can properly invalidate application invalidated sessions in the WebSphere eXtreme Scale client. Interim Fix 7.1.0.4 ensures that the 7.1.0.4 client that is used by WebSphere Application Server Hypervisor Edition Version 8.0 and IBM Web Application Pattern Version 2.0 properly invalidates application invalidated sessions in the WebSphere eXtreme Scale client. You can download the fixes from Fix Central at http://www.ibm.com/support/fixcentral. Search for APAR 52202. If you are using IBM Workload Deployer Pattern for Web Applications Version 1.0.0.3 and WebSphere Application Server Hypervisor Edition Version 7.0, download and apply Interim Fix 7.1.0.3. If you are using IBM Web Application Pattern Version 2.0.0.0 and WebSphere Application Server Hypervisor Edition Version 8.0, download and apply Interim Fix 7.1.0.4.