Bug 1841030
Summary: | RHV upgrade for 4.3 to 4.4 fails for IBRS CPU type | ||
---|---|---|---|
Product: | [oVirt] vdsm | Reporter: | Roman Hodain <rhodain> |
Component: | General | Assignee: | Lucia Jelinkova <ljelinko> |
Status: | CLOSED DUPLICATE | QA Contact: | Nikolai Sednev <nsednev> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | --- | CC: | ahadas, bugs, ljelinko, michal.skrivanek, rbarry, sbonazzo |
Target Milestone: | ovirt-4.4.1 | Flags: | pm-rhel:
ovirt-4.4+
pm-rhel: devel_ack? |
Target Release: | 4.40.20 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | vdsm-4.40.20 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-06-29 08:12:08 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1837266 |
Description
Roman Hodain
2020-05-28 07:57:54 UTC
Sandro, are we even supporting in-place no redeploy HE? It seems it indeed disappeared from cpu flags which is a problem for Name-IBRS specifically since that's the only one where we use "Name,+flag" instead. We can probably change that to Name-IBRS safely even for older Cluster Levels (In reply to Ryan Barry from comment #1) > Sandro, are we even supporting in-place no redeploy HE? Not sure I understood the question. Hosted engine upgrade flow from 4.3 to 4.4 requires a host reinstall with 4.4 followed by re-deploy of hosted engine with restore of the engine from backup. Does this answer? (In reply to Ryan Barry from comment #1) > Sandro, are we even supporting in-place no redeploy HE? Just to make it more clear. It is not an in-place upgrade. Everything is redeployed. The problem is the cluster CPU type which is set in the cluster in the DB which is restored. The new host is added to that cluster and has to comply with the CPU type set there. In my case, I used one with IBRS. The stage when the deployment waits for the host to become up fails as the host flips to the non-operational state due to the missing flag. We still have vdsm-4.40.19-1.el8ev.x86_64.rpm 2020-06-04 available to QA. I think that this bug is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1837266, because I used IBRS hosts too and the upgrade failed. As 1837266 was opened 2020-05-19, prior to this very bug, I think we should close it as a duplicate to 1837266. I agree. What about you, Arik? Right *** This bug has been marked as a duplicate of bug 1837266 *** |