Simplivity Upgrade Manager

[sampiyonts]

Hello,

Try to upgrade 3.7.9 to 3.7.10 , 

Update manager failed inventroy not found,

[Praveen_M]

Hi There,

When you run the Upgrade manager what are the components you have selected?
Kindly do not select the Esxi and firmware. Try to complete the upgrade one by one.
Also always contact HPE SimpliVity team for the pre-upgrade check before initiating the upgrade so that you can initiate the upgrade without any data lose.

HPE SimpliVity OmniStack 3.7.9 Interoperability Guide - https://support.hpe.com/hpsc/doc/public/display?docId=a00072859en_us

HPE OmniStack 3.7.9 for vSphere Upgrade Guide - https://support.hpe.com/hpsc/doc/public/display?docId=a00072854en_us

[dhooley]

Hi @sampiyonts ,

Typically when we get inventory not found it means there is an issue with node authentication to vCenter.

We would need to run the dsv-digitalvault command set to resolve this issue on all nodes and check for other possible scenarios. The best action at this point would be a support case for us to assist in greater detail.

Hope this helps,

David

[Stor_Mort · Accepted solution]

I've also seen that happen when the OVC has needed a reboot. 

[gustenar]

@sampiyonts 

I believe this is what you're running into, please check this article:

https://support.hpe.com/hpsc/doc/public/display?docLocale=en_US&docId=mmr_sf-EN_US000061620&withFrame

Thanks,

[SimonHorwood]

Hi

I had the same issue with the Upgrade Manager going from 3.6 to 3.8, and support suggested I use the CLI which worked fine!

These are the steps upgrade manually:

• svt-vm-show --cluster 'Cluster_Name'   --> to verify the VMS have HA Sync
• Command to upgrade: svt-software-upgrade --omnicube --pkgpath /mnt/svtfs/0/9329928e-5ca9-425e-b364-691283ca415c/.svtupgrade/SimpliVity-OmniCube-Software-revA-3.7.8.232.tar
• tail -f /var/log/svt-upgrade.log   ---> to follow the upgrade
• svt-software-status-show  --> to verify the upgrade has been successful
• svt-software-commit   ---> run this on one node to commit upgrades after they have been completed on all nodes

Good luck - I would try the other methods before the CLI 

[cheesi]

Hi,

i made already 3 upgrads always over the CLI becaus the Upgrade manager never works. I guess this software is not really usable. Next week i will update von 3.7.8 to 3.7.10 hoppfully with the upgrade manager

[fahlis]

Hi!

I've seen this issue in several of my deployment. Not sure why but use vCenter IP Address instead and it always work. At least for me and I have taken onto it as a best pratcice. I got the tip from HPE Support first time I ran into it with 3.7..6

Br / Tony

[cheesi]

Today i treid it again with the Upgrade Manager but no sucess 

Today i got a total new Error: java.io.IOException: Error writing request body to server after i selected the Cluster i get this Error. So the beta testing goes on.

[TomiKarlsson]

I had the same problem yesterday trying to upgrade from 3.7.9 to 3.7.10. Had to use the CLI instead.

/Tomi

[cheesi]

The funny stuff we have over 100 Simplivty nodes running. I always get the answer from HPE use the CLI xD with 100 nodes i start the upgrade on the first node and on the last one i can start again. Would be nice to get an answer why the Upgrade Manager wont work....

[policeman51]

Dumb question,

How do you get the files to:  /mnt/svtfs/0/<datastore_GUID>/.svtupgrade/

I thought that uploading them via Upgrade Manager would do it, but nothing is there.

[Stor_Mort]

You can use an ssh-based file copy protocol like sftp with a client program like filezilla, scp or similar. Authenticate with your vSphere administrator account.

[policeman51]

Thanks for the reply.

I ended up opened a support ticket and they helped out.

[aranim11]

i trying to upgrade 3.7.8 to 4.0.1, I am facing same issue

kindly suggest in which location we have to copy the files

[s-]

Hi @aranim11 

Here is the link to download the 4.0.1.U1 software.

https://support.hpe.com/hpesc/public/swd/detail?swItemId=MTX_ee6db5e1e7e74efba1698a53c5

4.0.1U1 Upgrade guide.

https://www.hpe.com/psnow/doc/a00104903en_us

Hope it helps.

Regards,
Jaipal