hpe-upgrade-component--1.4.1-1 and 900.0.2-1 - where does the 900.0.2-1 come from?

[pirx]

Can someone please explain to me the difference between hpe-upgrade-component--1.4.1-1 and 900.0.2-1. vLCM tells me that with latest HPE AddOns that were released today I would downgrade this component to 1.4.1 as 900.0.2.-1 is installed (it was same with older AddOns). I checked the content of HPE AddOns package and indeed 1.4.1 is included. But somehow an all of my hosts version 900.0.2-1 is installed and jut don't find anything about that version. There is nothing in HPE-VMware-Recipe.pdf

[Vijayakannan]

Hello,

You are trying to upgrade from Gen 10 portfolio servers with Gen 11 compatible add-ons.

I recommend to use the Gen 10 compatible latest add-ons. 

Thanks.

[pirx]

@Vijayakannan 

On the download pages and in vLCM there is no indication that this AddOn 2022-12-20 is only for Gen11 servers! It's the general AddOn for HPE Proliant Servers. And as I wrote before, the hpe-upgrade-component 900.0.2-1 was already installed before I used the latest AddOn package (which includes hpe-upgrade-component 1.4.1-1). 

So what is the difference between hpe-upgrade-component 900.0.2-1 and 1.4.1-1, I can't find anything about 900.0.2-1.

[RaviTyagi]

Hello Pirx,

Greetings of the day !,

We would request you to create a support case with us for further investigation.

https://www.hpe.com/us/en/contact-hpe.html

Regards,

RRT 

I am an HPE Employee 

[pirx]

I've created case hardware 5370396895, let's see how this works out.

[pirx]

Didn't get any feedback yet, but I found out that hpe-upgrade-component package version 900.0.2-1  is part of the predefined non-critical patch baseline. Due to the high version number of 900... the regular packages with versions 1.4.x will always be reported as outdated.

I don't really get this, I can't be the first one to notice this. And as this is a prefinded baseline I don't see that I could change anything about it than to manually blacklist the package in this baseline. But this looks broken by design or what am I missing?

[Johannes_we]

Did you ever find a way around? 

Having the same issue here.

[pirx]

You have to manually replace the version 900 with lastet version (1.4.1) before you start your first remdidiation. At some point in the past HPE had the great idea to push this package with version 900 to the update repo. And with that it will stay there as package with this highest version number until hell freezes over. It will always be installed if you do not overwrite it in the components section. And if you already have "downgraded" to 900 you have to manually unistall it with esxcli first, reboot, recheck compliance....

I opened a case a few months ago and after some time support understood the issue, but there is not quick solution. As I wrote in a different place, HPE hardware is nice, but everything else is so utterly and completely broken.

[Johannes_we]

Luckily i have my "update script" already in place that can deal with broken packages and removes those crappy dependencies.

I´m with you, HPE is sadly not a good software company in that sense.

[TQ12]

I ran into the same problem with that component.
But I WANT to update that component but that image builder says:
"Downgrades of manually added Components HPE Upgrade Component(900.0.2-1) in the desired Addon HPE-Custom-AddOn are not supported."  

The installed component is older then the selected new one because it is for ESXi7 and the new one is the newest for ESXi8.

So I can not upgrade those ESXi from v7 to v8 because I am "downgrading" that hpe-upgrade-component.

I do not know what that image builder is looking for but I assume it is the component name.

Any ideas how to get that new component accepted?

[pirx]

Seem there was an updated package released by HPE. HPE Upgrade Component    901.1.4.9-1.

Fascinating that the 900 version was in the repo for more than 2 years, breaking all the updates. of this package.

[TQ12]

I had to deinstall that 900 vib manually on my ESXis in order to get them upgraded.
What a mess ....

[stefanogermani]

hello

in the hp package for esx7 there is a vib:

hpe-upgrade 901.1.4.9-1OEM.700.1.0.15843807

I can't understand what it's for. It is only present in the custom ISO and I can't find the name in the single downloads for single installation.

I've looked everywhere, but no one explains what it is

helpme

thanks

[DanCernese]

Sorry there is no clear explanation.  This component has existed ever since HPE produced custom images (e.g. ESX 6, 7,  and v8.x) in order to ensure our components did not prevent upgrades and to prepare (such as obsoleting old services and preparing for new versions) for an upgrade of the ESXi OS/kernel and drivers.

[edit] I have edited my post four times to try and determine why "8" keeps getting removed.. something strange going on here.

[pirx]

That problem should have been solved a few months ago and root cause was bad version mangement by HPE / that the version is online repository was never updated properly with the right version. Version 900.0.2-1  was replaced by hpe-upgrade-component--901.1.4.9-1OEM.700.1.0.15843807 back in August. That was the solution for my now closed case. But looking at my vLCM repo I don't find this new version.