Hide Forgot
Description of problem: In Section 5.3. Upgrading a RHEL-Based Self-Hosted Engine Environment, it states that "To upgrade your Red Hat Enterprise Virtualization 3.6 self-hosted engine environment to Red Hat Virtualization 4.0, the Manager virtual machine must be upgraded from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7. After the Manager is upgraded you can update the self-hosted engine hosts, and any standard hosts, to 4.0." This section should link the customer to the procedure for doing an in-place upgrade of RHEL 6 to RHEL 7 (which is what I am assuming this procedure is telling us to do). It should link to this kbase article: https://access.redhat.com/solutions/637583 However, if I read further down in this section of documentation, it confuses me a bit because I see the following text: Important The upgrade utility builds a new Manager based on a template. Manual changes or custom configuration to the original Manager such as custom users, SSH keys, and monitoring will need to be reapplied manually on the new Manager. So, is this procedure supposed to upgrade the RHEV-M in place or is it building a new RHEV-M based on a template?
According to Bug 1380881, Engineering says that in place upgrading of RHEL 6 to RHEL 7 is not supported for hosted-engine. So, perhaps the request here should just be to make the wording clearer. To me, when it says "the Manager virtual machine must be upgraded from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7", that means to do an in place upgrade. Also, further down it says "On the Manager virtual machine, enable the required repository. # subscription-manager repos --enable=rhel-7-server-rhv-4.0-rpms" which is not possible to enable because the RHEV-M is running on RHEL 6 and the repo that needs to be enabled is a RHEL 7 repo.
*** Bug 1380881 has been marked as a duplicate of this bug. ***
I am going through the step for HE upgrade from 3.6 to 4.0 in the SHE guide[1] and it is not very clear. We should update it ASAP, since otherwise, if following incomplete instructions and guessing may break the environment in irrecoverable way. Setting sev to urgent. Suggestions to apply: 1. Specify the comment#2 from this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1380881#c2 We probably should elaborate a little bit more about the actual upgrade process in the docs, so that in case anything fails it will be more clear for the end user at what step and what has happened? We already have an "Important" note stating we are using some upgrade utility. So we just need to make it a bit more clear and detailed and to make sure the above clause is related to this note in more logical way. 2. Step 3 in current steps are incorrect, you cannot add rhel7 repo on rhel6 OS. ~~~ 3. On the Manager virtual machine, enable the required repository. # subscription-manager repos --enable=rhel-7-server-rhv-4.0-rpms ~~~ How this is supposed to work? [1] https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/single/self-hosted-engine-guide/#Upgrading_the_Self-Hosted_Engine
*** Bug 1382546 has been marked as a duplicate of this bug. ***
This content has been published to: - https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/single/self-hosted-engine-guide/#Upgrading_the_Self-Hosted_Engine