ZZ00236: VIL ISSUES UPDATING LOCATION OF REPOSITORIES.

2.3.0.1-CSI-ISCO-IF0009
IBM SmartCloud Orchestrator Interim Fix 7 for 2.3.0.1
IBM SmartCloud Orchestrator Interim Fix 6 for 2.3.0.1
IBM SmartCloud Orchestrator Interim Fix 5 for 2.3.0.1
IBM SmartCloud Orchestrator Interim Fix 3 for 2.3.0.1
IBM SmartCloud Orchestrator Interim Fix 2 for 2.3.0.1
IBM SmartCloud Orchestrator Interim Fix 4 for 2.3.0.1
IBM SmartCloud Orchestrator Interim Fix 8 for 2.3.0.1

APAR status

• Closed as program error.

Error description

• After adding another VMware Template to the VMware Cluster
  associated with a SCO VMware region, we see the image
  "windows_sco23" listed in OpenStack:
  [root@rs1 ~]# nova image-list
   ID         | Name           |  Status | Server |
  42163316... | windows_sco23  | ACTIVE  |        |
  
  However VIL shows the following message:
  
  Basic index windows_sco23 // Canceled //
  Click here for error details
  COPIML116EtaskAborted
    [Error]
  COPIML116E An unexpected event interrupted the task execution.
  Cause
  COPIML606E Additional details about the failure can be found in
  the Virtual Image Library log files.
  
  
  VIL SystemOut.log shows:
  [3/23/14 9:25:19:962 EDT] 0000014e ImageLibraryO I
  ImageLibraryObject lock acquired for windows_sco23: true.
  Number of Lock: 1. Lock key: feebdfe1...
  [3/23/14 9:29:57:242 EDT] 0000014e ImageLibraryO I   Disk for
  image windows_sco23 lock released. Number of lock: 0. Lock key:
  feebdfe1...
  
  
  vilProxy in SCO 2.3 GA can crash if it receives some unexpected
  request. IP/port scans can cause this issue.
  
  This is fixed in SCO 2.3.0.1
  
  The Synch of SCO repository is failing because of a particular
  condition due to wrong credentials used some days ago to
  register VMware Regions. In order to fix this SCO L3 provided a
  test fix.
  

Local fix

• We recycled vilProxy service and the sync now completes after
  ~15 hours.
  

Problem summary

• The Synch of SCO repository is failing because of a particular
  condition, in this particular scenario the location information
  is not updated.
  

Problem conclusion

• The synch method has been modified in order to update also the
  location information during the synchronization.
  

Temporary fix

Comments

APAR Information

• 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