| Summary: | [Docs] [SHE] Upgrading a RHEL-Based Self-Hosted Engine is wrong - ignores RHEL7 and wrong repos | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Jiri Belka <jbelka> |
| Component: | Documentation | Assignee: | Julie <juwu> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Andrew Burden <aburden> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.6.0 | CC: | adahms, gklein, jbelka, lsurette, rbalakri, yeylon, ykaul, ylavi |
| Target Milestone: | ovirt-3.6.2 | ||
| Target Release: | 3.6.2 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-02-09 06:25:14 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: | |
|
Description
Jiri Belka
2015-12-22 13:01:54 UTC
Assigning to Julie for review. Hi Jiri,
Thanks for filing this bug. On further investigation, I think we should differentiate between two use cases of upgrading RHEL hosts for 3.6:
1. Upgrading from a 6.x host to 7.x host for RHEV 3.6 -> need to tell customers how to upgrade or re-install the base OS to 7 first before enabling the 3.6 repos. Could you confirm what is the recommended method or what methods are supported?
* Can user use upgrade button in the Admin Portal to upgrade a 6 host to 7 or reinstall a host as 7?
* If user chooses to upgrade their 6 to 7, should they follow the recommendations in the RHEL guide https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Migration_Planning_Guide/chap-Red_Hat_Enterprise_Linux-Migration_Planning_Guide-Upgrading.html#chap-Red_Hat_Enterprise_Linux-Migration_Planning_Guide-Upgrading_from_RHEL6
2. Upgrading from 7.x to the latest 7.x for RHEV 3.6. -> just need to update the procedure with the right repos.
Kind regards,
Julie
(In reply to Julie from comment #3) > Hi Jiri, > Thanks for filing this bug. On further investigation, I think we should > differentiate between two use cases of upgrading RHEL hosts for 3.6: > > 1. Upgrading from a 6.x host to 7.x host for RHEV 3.6 -> need to tell > customers how to upgrade or re-install the base OS to 7 first before > enabling the 3.6 repos. Could you confirm what is the recommended method or > what methods are supported? there's WIP in this area, it should work this way - first cluster has to support rhel6 and rhel7. > * Can user use upgrade button in the Admin Portal to upgrade a 6 host to > 7 or reinstall a host as 7? not supported. > * If user chooses to upgrade their 6 to 7, should they follow the > recommendations in the RHEL guide > https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/ > html/Migration_Planning_Guide/chap-Red_Hat_Enterprise_Linux- > Migration_Planning_Guide-Upgrading.html#chap-Red_Hat_Enterprise_Linux- > Migration_Planning_Guide-Upgrading_from_RHEL6 there's WIP in this area, currently it seems we will support removal, reinstall, re-adding the host while its cluster would support mixed RHEL versions. > 2. Upgrading from 7.x to the latest 7.x for RHEV 3.6. -> just need to update > the procedure with the right repos. > > Kind regards, > Julie i was mostly complaining about bad repos, not about upgrade/migration procedure. |