Omnistack Upgrade from 4.0.1.184 to 4.2 failed

[Kalagan76]

Hello,

I'm trying to upgrade one node from Omnistack 4..0.1.184 to 4.2 but the upgrade failed everytime.

I don't know what to check or where to look at and i can't contact the support anymore.

the Message in Simplivity Upgrade Manager only says: Failed. The Upgrade failed.

Any help would be welcome.

Regards,

david.

[GM_M]

Hi Kalagan76 

Please do check this link for compatability of your appliance to Omnistack version 4.2

Thanks and Regards,
Manoj.

[Kalagan76]

Hi,

We already checked this documentation and everything is Ok. We should be able to upgrade our Omnistack from 4.0.1 to 4.2.
Anyway, as i said, everytime the process failed.
in the omnistack, the logs show the following error:

ClusterFedData.pm:146 Util::ClusterFedData::getClusterNodeToMgmtIpMap - Failed to get map: TaskException magic code '38' (see errors.xml to decode) at /scratch/upgrade/src/os/upgrade/install/Util/SvtControl.pm line 116.

[Mahesh202]

Hi Kalagan76

looking at the error message that was shared, it would require a log analysis to be done to determine the cause of this error. I would suggest that you contact HPE SimpliVity technical support and log a ticket to resolve the issue.

Regards
Mahesh.

[Kalagan76 · Accepted solution]

Hello,

Finally we've been able to solve our problem by running the following command:

dsv-update-vcenter --server vcsaip --username 'administrator@vsphere.local' --password 'vcsapassword'

FYI, we had to do a vcenter roll back becasue we first upgraded our vcenter from 6.7 to 7.03 while our omnistack were in 4.0.1.

Thanks for your help.

Regards,

David.

[Mahesh202]

Hi Kalagan76

I am glad to have heard that you were able to resolve the problem by running the dsv-update-vcenter command!
The HPE Tech Support recommendation for log analysis was made to ensure a thorough understanding of the problem and verify whether there were any issues with compatibility, misconfigurations, or unexpected failures during the upgrade. Logs can help identify patterns, errors, and warnings that may not seem obvious now, but may cause future problems.

Do get back to us, if you need further assistance.

Regards
Mahesh.