Description of problem: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/upgrade_guide/upgrading_to_red_hat_virtualization_manager_4.1 doesn't mention engine-upgrade-check but we mention it for updates of micro releases in same minor release. Version-Release number of selected component (if applicable): 4.1 How reproducible: 100% Steps to Reproduce: 1. check if '3.2. Upgrading to Red Hat Virtualization Manager 4.1' mentions engine-upgrade-check 2. 3. Actual results: missing Expected results: should be there Additional info:
Assigning to Byron for review. Byron, we've never included engine-upgrade-check in the context of a version-to-version upgrade before, so it might be worth confirming what the expected user behaviour is (e.g. 4.1 is released, does a customer on 4.0 need to run engine-upgrade-check to know that 4.1 is available, if they have to enable the 4.1 repos to do so anyway?)
This content has been published to: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html-single/upgrade_guide/#Upgrading_to_Red_Hat_Virtualization_Manager_4.1