Posted by: MikeLaverick
Coming of tweet from Eric Sloof, and from a blog post by Duncan Epping.
It looks as if VMware have released a U1-A, another sub-update to their update – shades of Service Pack 1a for Windows? I guess you could say that. The new update address the HP Insight Management Agent upgrade bug that reared its ugly head during the Thanksgiving Holiday period, which initiated an “August 12th” response from VMware in the form of announcements and eventually lead to them withdrawing U1 from VMware Update Manager.
The download page for U1-A also mentions a disconnect bug in ESXi that would occur after upgrading vCenter 4.0 to vCenter 4.0 U1.
The U1-A does NOT address this issue – and ESXi customers are advised NOT to upgrade until there is fix. That’s little comfort to people like me who have. I have ESXi host that repeated disconnects from vCenter even though its pingable. A restart of the network and management agents does not fix it.
Verdict? I will wiping the ESX host and putting ESX ‘Classic’ in the New Year.
As for U1. The jury is out on its quality. I upgraded because I wanted to use View4. Actually, View4 does work without the update – but to do so is unsupported. I’m now wondering if I should have bothered with U1.
I did a perfectly functional SRM4.0 deployment, however since U1 I’ve had nothing but problems – networking problems between the SRM and the vCenter. The trouble is it’s hard to conclude these problems are the fault of U1. Although nothing changed in my lab environment accept the U1 roll-out and the ‘repair’ of SRM that has to happen afterwards.
I guess should take heart. My woes are not in a production environment. But a lab environment. Rolling out U1 was a risk, but one that was quite small. I’ve decide to stop work for the rest of the year. I’m all tuckered out from 2009. I have course to teach next week in Swindon – and then its Xmas week. So I think I will leave the broken environment I currently have where it is – and start a fresh in the New Year.