On Fri, Jul 17, 2020 at 10:58 AM Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Fri, Jul 17, 2020 at 10:54 AM Martin Perina <mperina@redhat.com> wrote:
Hi Gianluca,

that's very strange error, because I'm 100% sure we are using yum module with Python3 in several other roles including adding host to engine or upgrading host and so far I haven't heard any issue with ansible 2.9.10 and yum module.

Gobinda, wouldn't enforcing python interpreter version help there?


Regards,
Martin


I have a very clean install from 4.1.1.1 node ng iso anf I'm the third to notice that with this release.
The engine deployment is going on. Not finished yet, but to have ti go I had to modify, with the same strategy ("use: dnf" with package module and use "package" instead of "yum" and also specifying "use: dnf") in these files under /usr/share/ansible/roles:

ovirt.engine-setup/tasks/engine_setup.yml
ovirt.engine-setup/tasks/install_packages.yml
ovirt.hosted_engine_setup/tasks/install_packages.yml
ovirt.hosted_engine_setup/tasks/create_target_vm/03_hosted_engine_final_tasks.yml
ovirt.hosted_engine_setup/tasks/install_appliance.yml

Gianluca

The installation from the iso was with all default values.
The only "non standard" thing, if we want it to call this way is that before running the wizard, on the host I pre-installed the appliance package, to shorten the deploy phase hereafter.
And to do it I executed, because of habit:
yum install ovirt-engine-appliance

instead of "dnf install...", but I think this doesn't influence ansible autodetect when using "package" module or the error about python2 when using "yum" module...

Gianluca