A fix is available
APAR status
Closed as program error.
Error description
Problem description: The customer changed 1 ESXi host to maintenance mode for a cluster. when the customer confirmed hypervisor screen of SCO, the status of this hypervisor became error with "can not delete hypervisor because instance exists." And the customer confirmed the information of memory usage rate of Cluster can not be collected. This problem is caused by the return of rest API /targets is null.
Local fix
Problem summary
PROBLEM SUMMARY *********************************************************** * THE VMWARE HYPERVISOR DOES NOT WORK AFTER ONE ESXI HOST CHANGE TO MAINTENANCE MODE. ********************************************************** * PROBLEM DESCRIPTION: The customer changed 1 ESXi host to maintenance mode for a cluster. when the customer confirmed hypervisor screen of SCO, the status of this hypervisor became error with "can not delete hypervisor because instance exists." And the customer confirmed the information of memory usage rate of Cluster can not be collected. ************************************************************* * RECOMMENDATION: This issue has been fixed in SCO2.3 FP1, so to fix this permernately, we recommend to update to SCO2.3 FP1. If you want to fix it in SCO2.3 GA, you can try the steps to update SCE in next section.
Problem conclusion
This problem is caused by the return of rest API /targets is null. This fix has delivered in SCO2.3 FP1, so to fix this permernately, we recommend to update to SCO2.3 FP1. If you want to fix this issue is SCO2.3, you can update SCE 3.1.0.3-IBM-SCE-IF003-201403032030.zip with following steps: 1) Download the package: 3.1.0.3-IBM-SCE-IF003-201403032030.zip at https://boegsa.ibm.com/projects/s/scol3fp/SCO-2.3/3.1.0.3-IBM-SC E-IF003-201403032030.zip 2) Create a directory on the local file system of the computer running the IBM SmartCloud Entry 3.1 application. For example: /tmp/repos/ 3) Extract the update package (zip) to the directory created in the previous step. 4) start the osgi CLI with the command below: telnet localhost 7777 5) From the IBM SmartCloud Entry OSGi console, type: addrepo file:<path> Where path is the full file path to the directory into which the update zip was extracted. For example: addrepo file:/root/hwp/SCE-ifix 6) Type installupdates The CLI output from the installupdates command should indicate installation success 7) Type "disconnect" to exit the osgi console 8) Restart sce service 9) Wait 30 seconds/2 minutes, depending on your vmware (number of templates/VMs) and finally start openstack-smartcloud service NOTE: A resynchronize repository action on VIL repositories could be needed to restore correct system functionality This ifix is on top of SCE 3.1.0.3, if you have not update to SCE3.1.0.3, then you need to update to SCE 3.1.0.3 first.
Temporary fix
Comments
APAR Information
APAR number
ZZ00225
Reported component name
SMRTCLOUD ORCHS
Reported component ID
5725H2800
Reported release
230
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-02-28
Closed date
2014-03-24
Last modified date
2014-03-24
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
SMRTCLOUD ORCHS
Fixed component ID
5725H2800
Applicable component levels
R230 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS4KMC","label":"IBM Cloud Orchestrator"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"230","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
03 November 2021