Red Hat Bugzilla – Bug 1297266
[Docs][Upgrade][3.6] Upgrade Guide needs to cover how to upgrade RHEL6 clusters to RHEL 7 clusters for 3.5 cluster compatibility
Last modified: 2016-03-09 19:46:35 EST
The current upgrade instructions only cover updating el6 to the latest el6 and el7 to the latest el7. It should cover getting from el6 cluster to el7 cluster scenario for upgrading to 3.6 with 3.6 cluster compatibility version.
Before BZ#1241149 is verified, users will need to follow the instructions similar to https://access.redhat.com/articles/1390733
Once BZ#1241149 is verified, just put the rhel6 host in the cluster into maintenance one by one and re-install it with rhel 7. My understanding is both re-installing and upgrading are supported.
This bug tracks the addition of the manual cluster upgrade information in https://access.redhat.com/articles/1390733 to the Upgrade Guide, to provide users an upgrade path for GA. The new content should reference the detailed prerequisites for live migration available in the Virtual Machine Management Guide:
The in-cluster upgrade feature, when it becomes available, will be documented in bug 1301447.
For the RHEV 3.6 GA we need the kbase to be in the guide without the in cluster process.
Assigning to Dayle for review.
Dayle, see the instructions in Comment 1. The procedure from the kbase should be added to the Upgrade Guide, probably as a standalone topic. At the moment, because clusters in RHEV cannot include a mix of RHEL 6 and RHEL 7 hosts, this is the only way to upgrade hosts from RHEL 6 to RHEL 7 for RHEV 3.6 (which supports only RHEL 7 hosts).
I think this should be added to Chapter 3. Upgrading to Red Hat Enterprise Virtualization 3.6 as it is a task you need to do after you upgrade the Manager.
The work flow is like this:
1. Upgrade the Manager to 3.6
2. Upgrade existing RHEL6 hosts as RHEL7.
* live vm migration is mentioned so this can be done in production environments where you don't want to shut dowm the vm to perform a RHEL base OS upgrade
* For RHEV-H, you can upgrade RHEV-H 6 to RHEV-H 7 from the Administration Portal.
* For RHEL-based hypervisors, advise users to reinstall or upgrade. I believe reinstalling is recommended as the upgrade path provided in the rhel guides are relatively complex.
3. Post upgrade task- change cluster and data center computability version to 3.6.
Without step2, even though the Manager is upgraded to 3.6, the cluster and data center computability version can only remain at 3.5 as RHEL6 hosts are not supported in 3.6 compatibility.
Please let me know if you have any questions.
sorry for the typos:
Thanks for the info. I've changed you to the QE contact on the merge request, as discussed, and I've edited the section quite a bit. I've added some extra steps to "Procedure 3.2. Live migrating virtual machines from a version 6 cluster to a version 7 cluster" for upgrading hosts, as well as some links. It's all in Git, ready to be checked.
However, two questions still:
* I can't find any instructions to upgrade a RHEV-H 6 host to a RHEV-H 7 host via the Admin Portal (and would like to add a link to a procedure if possible). Can you point me to something, or is the instruction here sufficient?
* Should we add a step about migrating VMs to another host while another host is being upgraded?
Thank you for reviewing,
Upgrading RHEV-H 6 to 7 is the same as updating within the same major version so the instructions in https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.6-Beta/html/Upgrade_Guide/Updating_Red_Hat_Enterprise_Virtualization_Hypervisors1.html apply. I have added the instructions in your procedure.
The vm migration step should be done before upgrading a host as you want the host to have no virtual load before upgrading or re-installing it.
I have also update the ulink format to what was agreed on.
Please have a look and see if you agree with the changes. Feel free to make edits. The content should cover what needs to be covered.
The changes you've made look excellent.
It makes much more sense to migrate the VMs before upgrading the host. Many thanks for clarifying the text and answering my questions.
Added a revision history entry.
Moving this bug to VERIFIED.
This has now been published in the 3.6 docs: