Hide Forgot
Description of problem: https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/paged/self-hosted-engine-guide/54-upgrading-a-rhev-h-based-self-hosted-engine-environment In the above process, 6th step is wrong: =================== 6. On the Manager virtual machine, enable the required repository. # subscription-manager repos --enable=rhel-7-server-rhv-4.0-rpms =================== First thing "rhel-7-server-rhv-4.0-rpms" is repo which need to enable on RHEL host, this is RHV-H-7 for 3.6 so we can't enable it on any RHV-Host. Second thing at this step, RHV-M is RHEL 6.X based HE-VM, so can't enable RHEL 7 repo on 6.X systems. Version-Release number of selected component (if applicable): NA How reproducible: NA Steps to Reproduce: NA Actual results: 6th Step is mentioned. Expected results: Need to remove wrong 6th step from document. without this step upgrade works fine. Additional info:
Can you please review the docs here? Do we need this step for RHV-H?
(In reply to Sarvesh Pandit from comment #0) > Description of problem: > https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/paged/ > self-hosted-engine-guide/54-upgrading-a-rhev-h-based-self-hosted-engine- > environment > > In the above process, 6th step is wrong: > > =================== > 6. On the Manager virtual machine, enable the required repository. > > # subscription-manager repos --enable=rhel-7-server-rhv-4.0-rpms > =================== > > First thing "rhel-7-server-rhv-4.0-rpms" is repo which need to enable on > RHEL host, this is RHV-H-7 for 3.6 so we can't enable it on any RHV-Host. > > Second thing at this step, RHV-M is RHEL 6.X based HE-VM, so can't enable > RHEL 7 repo on 6.X systems. > > Version-Release number of selected component (if applicable): > NA > > How reproducible: > NA > > Steps to Reproduce: > NA > > Actual results: > 6th Step is mentioned. > > Expected results: > Need to remove wrong 6th step from document. without this step upgrade works > fine. > > Additional info: It seems step '6.' is useless as appliance will replace current HE VM anyway. Should be confirmed by responsible QE team.
Agree with Jiri about step 6: hosted-engine --upgrade-appliance will create new VM so it useless to add channels to the old VM Correct me if I wrong: 1) The command --upgrade-appliance exists only under hosts with the 4.0 packages, so you will need to upgrade first hosts. 2) I must run upgrade of RHEV-H from the engine or via PXE, and not via package manager, so you do not need to run subscription manager commands
*** Bug 1401006 has been marked as a duplicate of this bug. ***
*** Git link: https://gitlab.cee.redhat.com/rhci-documentation/docs-Red_Hat_Enterprise_Virtualization/merge_requests/309 *** What's changed: Removed the incorrect step from the procedure.