ansible images using just ubi8

[camilamacedo86]

Description of the change:
Ansible images using just ubi8

Motivation for the change:

#1656

[camilamacedo86]

Hi @joelanford,

JFY. Not passing because of the usage of inotify. I am adding it with the download of the image and trying to check. It is just used here:

operator-sdk/internal/pkg/scaffold/ansible/ao_logs.go

Line 43 in 2ca5cb1

inotifywait -r -m -e close_write ${watch_dir} | while read dir op file

. What we can do is change this impl to do the same in another way.

TASK [debug] *******************************************************************
    ok: [localhost] => {
        "ansible_log.stdout_lines": [
            "/usr/local/bin/ao-logs: line 6: inotifywait: command not found"
        ]
    } 

[camilamacedo86]

/test e2e-aws-helm

[camilamacedo86]

/test e2e-aws-subcommand
/test e2e-aws-ansible

[camilamacedo86]

/test e2e-aws-ansible

[joelanford]

We should use yum install -y directly on the RPM url:

 && yum install -y https://rpmfind.net/linux/fedora/linux/releases/30/Everything/x86_64/os/Packages/i/inotify-tools-3.14-16.fc30.x86_64.rpm \

[joelanford]

@camilamacedo86 Is there some reason we're using pip in line 34 but pip3 in line 33? If so, a comment explaining why would be good, since I would think we would use pip3 across the board after upgrading to python 3.

/cc @fabianvf

[camilamacedo86]

It is required to install setuptools which is not satisfied with pip3
Maybe it can work with python3-setuptools. I will try.

[camilamacedo86]

Worked and I remember what happened. Previously, I faced an issue in the setup.py script to install ansible using pip3, however, it worked locally now. Probably it was because it was missing some of the upgrades made so far.

[camilamacedo86]

/test e2e-aws-go

[camilamacedo86]

Hi @joelanford,

I think it is OK to go now. WDYT?

[joelanford]

LGTM when CI passes.

Would like a review from @fabianvf before we merge.

[fabianvf]

/lgtm