Bug 1349745
Summary: | EL6 to EL7 cluster upgrade is not possible with hosted engine in the same cluster | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Roman Mohr <rmohr> |
Component: | ovirt-engine | Assignee: | Nobody <nobody> |
Status: | CLOSED NOTABUG | QA Contact: | meital avital <mavital> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 3.6.0 | CC: | bugs, dfediuck, lbopf, lsurette, mkalinin, rbalakri, Rhev-m-bugs, rmohr, sbonazzo, srevivo, stirabos, ykaul, ylavi |
Target Milestone: | ovirt-3.6.9 | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | hosted-engine | ||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-11-20 08:52:24 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Docs | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Roman Mohr
2016-06-24 07:08:50 UTC
Doron reminded me that Hosted Engine was explicitly out of scope for the el6 to el7 cluster upgrade policy. The documentation needs to be fixed. @Roy @Doron still I think we should fix the problem that starting the hosted engine on a different cluster than where it was imported should update the hosted engine VM. It currently still thinks that it is running in the old cluster. Opinions? We need a process for this use case, please provide one to document. (In reply to Yaniv Dary from comment #2) > We need a process for this use case, please provide one to document. There is a small bug hidden: When the HE-VM is started-on/migrated-to a host which is not part of the cluster where the VM was initially imported, the VM still thinks it is part of the old cluster. This has consequences for both upgrade processes: 1) InClusterUpgrade (critical for that one, but not officially part of the design scope): - No matter if you move the HE-VM to another cluster by migration or restart, you can't start the InClusterUpgrade because the cluster still thinks it has a not automatically migratable VM (the HE-VM) in the cluster. Only solution is to change the DB-Entry. 2) Normal upgrade (Move all hosts to a new cluster) After all hosts and VMs are on the new cluster, the original cluster still thinks that one VM is running in it (the HE-VM) and therefore you can't delete the old cluster after all hosts are migrated. That is probably not a blocker but can also only be solved with a DB-update. So we should do the following: 1) Make sure that the VM and the Cluster always know in which cluster the HE-VM is 2) Fix the documentation. It should describe the second scenario for the normal upgrade (instead of the InClusterUpgrade) as the default scenario. @Yaniv should we create a second bug for one of those? Bug 1351533 will solve the problem of making the HE VM migrating out-of-cluster and the cluster be updated properly under for the HE VM. Then the host would be able to go to maintenance, removed and the cluster would be able to be removed. Clearing doc text and flag, as this issue appears to have been fixed by bug 1351533. The code worked as expected detecting that the at least hosted-engine host was still on el6 so it proposed to abort upgrading the HE hosts first. |