Only specific version of Ansible is properly tested with specific RHV version and to prevent breakages of already released RHV we have introduced a version lock on specific Ansible release. But this caused an issue during upgrades which needed to be mitigated by KCS https://access.redhat.com/solutions/5480561 From RHV 4.4.5 we are going to provide correct ansible version in RHV channel, so we will no longer need subscription to ansible-engine channel and there should no longer be version lock issues with newer version of ansible from this channel
Hi Martin / Didi, Do we have a question/warning during engine-setup that the user should remove external ansible channels to avoid conflicts? If not, can we please add this? I know we are late in the game, but it is important. And it can be just a note at the end of the setup, so that should not add load to QE.
(In reply to Marina Kalinin from comment #4) > Hi Martin / Didi, > Do we have a question/warning during engine-setup that the user should > remove external ansible channels to avoid conflicts? No, we don't > If not, can we please add this? Definitely not in 4.4.5. The problem is complex, we can't rely on channel names (they can be completely different on Satellite setup). Not to mention, that this detection and error reporting would need to be done not only in engine-setup, but also in hosted-engine-setup and host-deploy, so quite complex solution. > I know we are late in the game, but it is important. And it can be just a > note at the end of the setup, so that should not add load to QE. As mentioned above, the correct solution would mean a change in engine-setup, hosted-engine-setup and host-deploy, so too complex change. If we agree that this is really needed, we need a new bug for that targeted to 4.4.6
(In reply to Marina Kalinin from comment #4) > Hi Martin / Didi, > Do we have a question/warning during engine-setup that the user should > remove external ansible channels to avoid conflicts? > If not, can we please add this? > I know we are late in the game, but it is important. And it can be just a > note at the end of the setup, so that should not add load to QE. In addition to comment 5, can you please clarify why this is important? In both ovirt-engine and ovirt-hosted-engine-setup packages, we require exactly ansible 2.9.17. (That's for RHV. oVirt's ovirt-engine requires ansible >= 2.9.0, ansible < 2.10.0). Does it matter if the user supplies this version of ansible using whatever possible means? Worst case, a 'dnf install/upgrade' will fail due to a conflict, if a newer version is available. A fix for this should be '--nobest', IMO, or some more specific manual dnf configuration, if needed - not adding more complexity to the installation code. I might be missing something...
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (RHV Engine and Host Common Packages 4.4.z [ovirt-4.4.5]), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2021:1185