Bug 1393686
Summary: | When putting hypervisor into maintenance, HostedEngine does not migrate | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Marcus West <mwest> |
Component: | ovirt-hosted-engine-ha | Assignee: | Martin Sivák <msivak> |
Status: | CLOSED DUPLICATE | QA Contact: | meital avital <mavital> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.0.4 | CC: | dfediuck, gklein, lsurette, mwest, oourfali, ykaul |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-11-23 11:51:42 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | SLA | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Marcus West
2016-11-10 07:25:23 UTC
Marcus, can you please give us the hosted engine logs too? A screenshot of the webadmin (Hosts and VMs tabs) would help us too. This might be a duplicate of https://bugzilla.redhat.com/1362618 Ah, no.. we still want the logs, but I just noticed the issue is in your steps: All automatic is disabled when you put the cluster to global maintenance. This includes the local maintenance migrations. Was there a reason for the global maintenance? If not, then this might be a DUP of https://bugzilla.redhat.com/1359499 Btw you might want to check for https://bugzilla.redhat.com/show_bug.cgi?id=1362618#c15 when testing with Global maintenance disabled. This part should be fixed in 4.0.5 iirc. Created attachment 1221044 [details]
migration stuck screenshot
I have tried to migrate HostedEngine by putting the host (intelh5) into maintenance. By checking the hypervisors, I can see that it has actually migrated successfully, but the gui only shows '0% completed'
*** This bug has been marked as a duplicate of bug 1362618 *** |