VMware Cloud Community
peetz
Leadership
Leadership

Latest Windows patches break PowerCLI ImageBuilder ?!

Hi all,

since yesterday I'm seeing strange errors when using the ImageBuilder cmdlet Get-EsxImageProfile. It is simple to reproduce: Open a PowerCLI session and run the following commands

Add-EsxSoftwareDepot https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml

Get-EsxImageProfile

The Get-EsxImageProfile cmdlet will throw the following error:

Get-EsxImageProfile : The parameter 'name' cannot be an empty string.

Parameter name: name

At line:1 char:1

+ Get-EsxImageProfile

+ ~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : NotSpecified: (:) [Get-EsxImageProfile], ArgumentException

    + FullyQualifiedErrorId : System.ArgumentException,VMware.ImageBuilder.Commands.GetProfiles

However, -name is NOT a mandatory parameter. Strangely enough, after seeing this error subsequent Get-EsxImageProfile commands will throw even weirder errors ... It looks like the whole PowerCLI session is corrupted in a way.

Weird is also that something like Get-EsxImageProfile "ESXi-5.5*" will work, but Get-EsxImageProfile "*" will throw the same error.

These errors did not happen before yesterday, so what was changed? This is a Windows 8.1 x64 machine, and I installed the latest Microsoft patches that were published this week. Another user (who was trying to use my ESXi-Customizer-PS script) reported a similar error on a fully patched Windows 7 x64 machine. I'm not sure if that affects 32bit and other Windows versions as well, but it seems to happen independently from the PowerCLI version. I was trying with PowerCLI 5.5 R2 on top of PowerShell 4.0 first, then upgraded to the latest PowerCLI 5.8 R1, but this did not make the error going away. The other user was using PowerCLI 5.8 R1 on top of PowerShell 3.0.

Can someone please confirm this behavior?

How do you file a bug for PowerCLI to address that to the development team?

Thanks

Andreas

Twitter: @VFrontDe, @ESXiPatches | https://esxi-patches.v-front.de | https://vibsdepot.v-front.de
Tags (2)
Reply
0 Kudos
8 Replies
LucD
Leadership
Leadership

Andreas, it seems this is a problem with XML file on the VMware site, not the PowerCLI cmdlets.

In fact users should see the same issue with PowerCLI 5.5 and 5.1.

VMWare is looking into it.

There is a bypass (see here).


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

Reply
0 Kudos
Gabrie1
Commander
Commander

Alan told me this bypass ONLY works when you run Get-ESXimageprofiles -name "ESXi-5.5.*" the first time in a session. If after that you run just get-ESXimageprofile, you get the error again.

http://www.GabesVirtualWorld.com
Reply
0 Kudos
LucD
Leadership
Leadership

Use the ZIP file instead of the online XML file,


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

Reply
0 Kudos
peetz
Leadership
Leadership

But yesterday evening I tried this on an old Windows 7 (32bit) Netbook that was not fully patched, and there I did NOT get these errors! Was running PowerCLI 5.0.1 though ...

This is why I'm thinking that it is linked to the latest Microsoft patches.

Twitter: @VFrontDe, @ESXiPatches | https://esxi-patches.v-front.de | https://vibsdepot.v-front.de
Reply
0 Kudos
LucD
Leadership
Leadership

I had the issue on a Win 8.1 before I applied the September patches


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

Reply
0 Kudos
ashukla02
Contributor
Contributor

This seems to be an issue only when we list all the available Image Profiles available in the depot. PowerCLI hangs there!

Workaround-- If PowerCLI session is hanged, restart the session and use a particular pattern to list the Image Profiles.

Example--

It is ok if we only list all 5.5/5.1/5.0 image profiles

</snippet>

PowerCLI C:\Program Files (x86)\VMware\Infrastructure\vSphere PowerCLI> Get-EsxmageProfile -name "ESXi-5.5.*"

Name Vendor Last Modified Acceptance Level

---- ------ ------------- ----------------

ESXi-5.5.0-20140701001s-no-... VMware, Inc. 8/23/2014 6:... PartnerSupported

ESXi-5.5.0-20140302001-no-t... VMware, Inc. 8/23/2014 6:... PartnerSupported

ESXi-5.5.0-20140604001-no-t... VMware, Inc. 8/23/2014 6:... PartnerSupported

ESXi-5.5.0-20140401020s-sta... VMware, Inc. 8/23/2014 6:... PartnerSupported

ESXi-5.5.0-20131201001s-sta... VMware, Inc. 8/23/2014 6:... PartnerSupported

............

.......

</snippet>

Same holds good for "ESXi-5.1.*" or "ESXi-5.0.*"

Reply
0 Kudos
J_Kolkes
VMware Employee
VMware Employee

Hi,

Anyone knows if there's a KB article to follow for when a solution to this issue is provided?

Thanks.

Reply
0 Kudos
peetz
Leadership
Leadership

Yes: http://kb.vmware.com/kb/2089217

It currently provides a workaround. Hopefully it will be really fixed with a future update of PowerCLI.

- Andreas

Twitter: @VFrontDe, @ESXiPatches | https://esxi-patches.v-front.de | https://vibsdepot.v-front.de
Reply
0 Kudos