VMware Cloud Community
BenLiebowitz
Expert
Expert
Jump to solution

Using VUM to upgrade host from 5.5 to 6.0

Hi,

I'm trying to use PowerCLI to upgrade some hosts from 5.5 to 6.0.  I'm not sure if it's failing because, if you do it manually via Update Manager, it prompts you to accept the EULA?

get-baseline -name "HP ESXi 6.0 U2" | remediate-inventory -entity $VMHOST -confirm:$false

This is the code i"m using.  This works fine when I try to install normal patch or extension baselines, but with the Upgrade baseline I'm having issues.

The error says the hardware is incompatible, but I know that isn't the case.  Everything has been verified on the HCL.

Here's my error:

remediate-inventory : 5/2/2017 10:45:26 AMUpdate-Entity    The

operation for the entity "VMHOST" failed with the following

message: "Hardware configuration of host VMHOST is

incompatible. Check scan results for details."

At D:\ps1\vmware\VUM_HostUpgrade.ps1:62 char:40

+ ... "HP ESXi 6.0 U2" | remediate-inventory -entity $VMHOST -confirm:$false

+                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo      : NotSpecified: (:) [Update-Entity], ExtendedFault
+ FullyQualifiedErrorId : Client20_TaskServiceImpl_CheckServerSideTaskUpda

   tes_OperationFailed,VMware.VumAutomation.Commands.RemediateInventory

c'mon Community Warrior LucD​, put on your cape and save me! Smiley Happy

Anyone?  Smiley Happy

Ben Liebowitz, VCP vExpert 2015, 2016, & 2017 If you found my post helpful, please mark it as helpful or answered to award points.
0 Kudos
1 Solution

Accepted Solutions
LucD
Leadership
Leadership
Jump to solution

I remember seeing something similar in the past.
A reboot of the ESXi node fixed the issue then.

Did you already try a reboot before doing the Remediate-Inventory.nn

And perhaps you should upgrade to the latest PowerCLI version.
The Update Manager module is improved.

Btw the new cmdlet is Update-Entity


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

View solution in original post

0 Kudos
2 Replies
LucD
Leadership
Leadership
Jump to solution

I remember seeing something similar in the past.
A reboot of the ESXi node fixed the issue then.

Did you already try a reboot before doing the Remediate-Inventory.nn

And perhaps you should upgrade to the latest PowerCLI version.
The Update Manager module is improved.

Btw the new cmdlet is Update-Entity


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

0 Kudos
BenLiebowitz
Expert
Expert
Jump to solution

You're probably right on the reboot..  the host I was getting the error on turned out to have a hardware issue.  I just did another one and used the update-entity cmdlet and it's working fine now. 

Thanks!

Ben Liebowitz, VCP vExpert 2015, 2016, & 2017 If you found my post helpful, please mark it as helpful or answered to award points.
0 Kudos