Created attachment 1247576 [details]
What hosted-engine --vm-status shows
Description of problem:
When putting the host running HE in maintenance mode through the RHV4 admin console GUI, the host prepares, moves VMs but appears stuck moving the HE. The HE shows 82% completed but never shows as compelted (preventing the maintenance mode in GUI). I can activate from maintenance mode on the host and retry but HE migration status shows as stuck on 82%.
Version-Release number of selected component (if applicable):
Often when migrating the host running the HE
Steps to Reproduce:
1.Select Host running SPM and HE and click maintenance mode, accept default (don't check take gluster offline)
2. Wait for a long time
3. Check CLI to ensure migration finished and HE is on new host.
Migration of HE shows 82% and doesn't finish. Shows running on old host in GUI yet hosted-engine --vm-status shows it running on new host
Maintenance mode entered and HE migration complete
Same issue here I beleive - https://bugzilla.redhat.com/show_bug.cgi?id=1377994
I tried closing and reopneing the Admin GUI
I set global maintenance afterwards
none of this helped
I am using gluster underneath as storage
Created attachment 1247577 [details]
GUI showing hung migration of HE
Created attachment 1247578 [details]
Host preparing for migration
Created attachment 1247579 [details]
Created attachment 1247580 [details]
I just updated the hosts and engine and it seemed to work when I did the maintenance mode on virt05 (instead of virt04). I will retry on virt04 and report results. I did the appliance upgrade (from virt05 using the hosted-engine command (instead of yum update)). I'm going to save the VDSM archives now in case they are useful, I also have a backup of the old engine. Let me know if anything else needs to be saved.
Seems to be handling migrations now after upgrading to ovirt-engine-22.214.171.124-0.1.el7ev.noarch
What did you tried to do, to upgrade using "hosted-engine --upgrade-appliance" tool from 3.6->4.0?
Please be aware that this tool was designed only for 3.6->4.0 upgrades.
For 4.0->4.1 you should use regular upgrade flow from the engine (repos, yum update rhevm*, engine-setup, etc.). Same for hosts.
I think I realized that and did the rollback. I will retest. Thanks for the clarification, not idea why I tried it that other way.
Closing due to the upgrade flow.
If this is reproducible on a clean supported upgrade flow please reopen with the reproduction steps.