vCenter plug-in shows wrong license count and cannot get upgraded

Hi TBajec,

Sorry for all of the questions.  What browser and version are you using to access the console?  Can you delete your browser cache, close up the browser and then log back in?

I see you mentioned build 1262 - did you mean 1272?  Could you verify the version you see after clearing your cache by clicking on the about link?  What is the update URL, current, and available versions shown on the update screen?

What happens after clicking update is to use the URL to find updated RPMs to apply.  It could be that the download of new RPM files is timing out or being interrupted on the network a manner we didn’t plan on or capture.  Another possibility is there weren’t really any updates to be applied but then the upgrade screen shouldn’t have been displayed.  That’s why I’m asking about the appliance version, update URL and browser version.  After the updates the appliance is always instructed to reboot, which may be happening even if there was nothing to do or a problem occurred.

There are a couple of programmatic checks that occur during the upgrade process.  After the reboot when logging back into the admin portal, if the code was able to detect an upgrade failure, a popup message should have immediately appeared. That being said there could be a failure that happened that we didn’t expect and don’t know about.  The support team can get the logs and take a closer look for you.

It’s unlikely there is anything wrong with your license.  If there were it would have let you know immediately when it was being uploaded.  The behavior you mention makes me suspect the browser’s javascript isn’t working as it should, but that’s just a guess.

Hope this helps.

Hi Michael,

thanks for the quick reply. i have cleared the browser cache and i can see the correct license now.

it is now "Unlimited". i also tried another update but i am still on version 1261 (sorry for the typo on the first post). also i can see the correct license now under dell management in the VC client. thanks for that.

but i still have the problem with the update. i tried it another time and still the same.

i can see that 1272 is available but nothing changes after running the update. the path is: http://linux.dell.com/repo/hardware/vcenter-plugin/latest. i can manually open that in the browser and see all the files there.

i have extracted the los and can see the below entries in the rpmupdate.log. for it it looks like the appliance can access the update path but cannot download it.

can that be a problem on your side? or should i check it with our networking team. however we do allow http and https and ftp from our servers.

 

cu

tom

 

Transaction Summary

================================================================================

Install 0 Package(s)

Upgrade 15 Package(s)

Total download size: 100 M

Downloading Packages:

http://linux.dell.com/repo/hardware/vcenter-plugin/latest/spectre/spectre-webclient-package-2.0.0-1138.1.noarch.rpm: [Errno 4] Socket Error: timed out

Trying other mirror.

http://linux.dell.com/repo/hardware/vcenter-plugin/latest/spectre/spectre-deps-2.0.0-1150.1.i386.rpm: [Errno 4] Socket Error: timed out

Trying other mirror.

　

Error Downloading Packages:

spectre-webclient-package-2.0.0-1138.1.noarch: failure: spectre/spectre-webclient-package-2.0.0-1138.1.noarch.rpm from Dell_VC_Plugin: [Errno 256] No more mirrors to try.

spectre-deps-2.0.0-1150.1.i386: failure: spectre/spectre-deps-2.0.0-1150.1.i386.rpm from Dell_VC_Plugin: [Errno 256] No more mirrors to try.

Hi Tbajec,

The appliance is just calling the linux "YUM Update" command against the repo location. The “Socket Error: timed out” messages you see are being piped directly from Yum. Could it be the network the appliance is on requires proxy settings to get to the internet? If so you can set those first in the admin portal before running the update.

Hope this helps.

Hi Michael,

we had to do a little trick. we set a timeout of 600 seconds on the yum.conf file on the appliance. with that we did not run into a timeout anymore and we could update the appliance.

anyway thanks for your help on that issue.