Description of problem: When upgrading RHV 4.0 with ovirt-fast-forward-upgrade, I get this warning: [ WARNING ] The following repositories are required for 4.0 - jb-eap-7-for-rhel-7-server-rpms [ WARNING ] The following repositories are enabled and not the main repositories for RHV 4.0 - jb-eap-7.0-for-rhel-7-server-rpms # yum repolist Loaded plugins: search-disabled-repos, versionlock repo id repo name status jb-eap-7.0-for-rhel-7-server-rpms/7Server/x86_64 JBoss Enterprise Application Platform 7.0 (RHEL 7 Server) (RPMs) 947 rhel-7-server-rhv-4.0-rpms/x86_64 Red Hat Virtualization Manager 4.0 (RHEL 7 Server) (RPMs) 330 rhel-7-server-rpms/7Server/x86_64 Red Hat Enterprise Linux 7 Server (RPMs) 26497 rhel-7-server-supplementary-rpms/7Server/x86_64 Red Hat Enterprise Linux 7 Server - Supplementary (RPMs) 339 repolist: 28113 But jb-eap-7.0-for-rhel-7-server-rpms is the repository indicated in the documentation: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.0/html/installation_guide/chap-installing_red_hat_enterprise_virtualization#Subscribing_to_the_Red_Hat_Enterprise_Virtualization_Manager_Channels_using_Subscription_Manager Version-Release number of selected component (if applicable): ovirt-fast-forward-upgrade-1.0.0-1.el7ev.noarch ovirt-engine-4.0.7.4-0.1.el7ev.noarch How reproducible: Always Steps to Reproduce: 1. Install RHV Manager with the repositories indicated in the documentation 2. ovirt-fast-forward-upgrade Actual results: Warning about repositories Expected results: No warning or the documentation fixed. Additional info:
There were recent changes in channels for older RHV 4.y versions around EAP channels, so most probably the tool needs to align with documentation and below KCS article: https://access.redhat.com/articles/4090791
Hi, > Version-Release number of selected component (if applicable): > ovirt-fast-forward-upgrade-1.0.0-1.el7ev.noarch This is the first release of ovirt-fast-forward-upgrade, customer need at least ovirt-fast-forward-upgrade-1.0.0-8.el7ev to get the changes Martin pointed in comment#1. Going to close this bug, fell free to re-open in case need additional help.