Description of problem: [4.4.3-8] failed to update packages in deploy because of new ansible-2.9.14 is available when we have version lock on ansible-2.9.13 Version-Release number of selected component (if applicable): ovirt-engine-4.4.3.6-0.13.el8ev.noarch ovirt-ansible-hosted-engine-setup-1.1.8-1.el8ev.noarch How reproducible: 100% Steps to Reproduce: 1. deploy hosted engine. Actual results: failed with the following error in TASK [ovirt.engine-setup : Update all packages] [root@hosted-engine-06 yum.repos.d]# yum update Last metadata expiration check: 0:43:02 ago on Sun 11 Oct 2020 11:03:41 AM IDT. Error: Problem: package ovirt-engine-4.4.3.6-0.13.el8ev.noarch requires ansible = 2.9.13, but none of the providers can be installed - cannot install both ansible-2.9.14-1.el8ae.noarch and ansible-2.9.13-1.el8ae.noarch - cannot install the best update candidate for package ovirt-engine-4.4.2.6-0.2.el8ev.noarch - cannot install the best update candidate for package ansible-2.9.13-1.el8ae.noarch (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) [root@hosted-engine-06 yum.repos.d]# Expected results: to fix this conflict between version lock and available packages Additional info: failed in live channels of 4.4.2 too
(In reply to Avihai from comment #1...) > Blocking engine and host deploy when reaching the "Update all packages" > stage. > Adding regression flag as this was seen in latest 4.4.3-8 DS build. > > > Issue also occurs on non hosted-engine hosts[1]: > > " > > 09:34:36 TASK [Update all packages] this is not a RHV task. If you have your own task doing "yum update" you have to fix it
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
Verified on ovirt-ansible-collection-1.2.0-0.3.el8ev.noarch
This bugzilla is included in oVirt 4.4.3 release, published on November 10th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.3 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.