Query: Problem with start upgrade Omnistack with upgrade manager

[Jpe_bastias]

Hi everyone

Recently run the upgrade manager for to upgrade omnistack from 4.0.1 to 4.1. my plataforma has a mva and 10 ovc.

when start de upgrade manager this show message "Cannot access the management virtual appliance. Verify that the management appliance is powered on and the accessible then, restart upgrade manager"

well, well I did and validate all that. but still I have the problem.  when seeing the mva through ui it does not show its status.

also try to deploy the mva again but it is not possible either.
any ideas.

I already opened a case but still without news.

[support_s]

System recommended content:

1. HPE OmniStack 4.1.0 for vSphere Upgrade Guide

2. HPE OmniStack 4.1.0U1 for vSphere Upgrade Guide

If the above information is helpful, then please click on "Thumbs Up/Kudo" icon.

Thank you for being a HPE community member.

[Jpe_bastias]

Yes, I'm follow the HPE OmniStack 4.1.0 for vSphere Upgrade Guide, but the guide not have like solve de problem the "cannot access the management virtual appliance MVA"
I'm stopped in this stage

[BPSingh]

Hello, 

Greetings!

Logs will tell more, however I see that you have already opened a case for further investigation.

Having said that, could you confirm if you are using Vcenter fQDN while logging to Upgrade Manager? 

If yes, please use IP address of Vcenter while logging to UM and check for the issue. 

[Jpe_bastias · Accepted solution]

Hellow. Greetings!

Yes, I already opened a case, and this is resolved. finaly the team support disabled the mva from federation. then when run the um this start without mva and now I will can upgrade the omnistack nodes.

I runed the upgrade manager with Vcenter IP address and also Vcenter FQDN.
I'm so Sorry I can´t give more details because i don't know what the team support exacly dit.

[MikeSeden]

The easiest way to solve the upgrade problem with the MVA is to remove the MVA(s) from the Federation. You can do the first steps:

1. dsv-mva-show    note the IDs of the MVAs

2. dsv-mva-delete --id <mva_id>      Do this for each of the MVAs

3. Go to vCenter and ensure that the MVAs are no longer in the inventory

4. Delete the Datastores from vCenter:   SimpliVity Federation > Backup Policies   System-Internal-MVA (policy)
You can see the Datastores of the MVAs from here- they can be deleted from this screen with [right click]> simplivity actions> delete datastore

5. svt-policy-delete --name System-Internal-MVA

At this point you will need to engage support to run a script which will "switch" the Fed from a MVA Federation to an Non-MVA Federation. After that you should have no problems with the upgrade. I would recommend not putting the MVA back in the Federation.