Hi Everyone,
We have recently updated our View v5.0 system to View v5.1 by closely following the instructions in the published upgrade guide.
Our VDI system seems to be working OK in general since this upgrade. However, we have encountered the following new issues. Just wondering if anyone else has experienced the same and/or may have any advice please ?.
- The view composer log file contains multiple instances of the following error when the cloning the master replica to create a pool (but clone & pool creation still works).
2012-06-26 17:42:10,000 | 31 | INFO | CommonLib.Util.Util - Will retry after 0 seconds. The retry number is 1.
2012-06-26 17:42:10,000 | VC thread | INFO | CommonLib.VcSubsystem.PropertyCollectorUpdateTracker - Got SimVcSubsystemException RequestCanceledFault fault was thrown by the VC server: https://na-vdi-vcenter.stud.ad.eiu.edu.au:443/sdk..
- When creating a pool with “Host Caching” enabled the system waits for 30mins at a “configure virtual disk digest” task within vCenter. During this period multiple instances of the following error appears in the View Composer logs (but pool creation eventually still works)
2012-06-26 17:54:22,971 | 30 | INFO | CommonLib.Util.Util - Will retry after 0 seconds. The retry number is 1.
2012-06-26 17:54:22,971 | VC thread | INFO | CommonLib.VcSubsystem.PropertyCollectorUpdateTracker - Got SimVcSubsystemException RequestCanceledFault fault was thrown by the VC server: https://na-vdi-vcenter.stud.ad.eiu.edu.au:443/sdk..
- When deleting a pool with “Host Caching” enabled the vcenter reportsthe VM replica has been deleted from the datastore. However, if you browse the datastore it’s actually still there and needs to be deleted manually.
- According the the VMWare View Admin Guide if you enable “host caching” on an existing pool the VMs within that pool should activate this feature after they next reboot. This is not happening in our environment; we can only get “host caching” activated for VMs if the pool is created with this option ON when it’s created.
Perhaps these are just some new bugs included in View v5.1 ?. Not a big deal so we are just working around them for now but it would be excellent to be able to fix these up.
Thanks