[WIP] run Ansible sanity tests against AWX collection

[AlanCoding]

Connect #4892

[softwarefactory-project-zuul]

Build failed.

• awx-api-lint : SUCCESS in 12m 08s
• awx-api : SUCCESS in 19m 28s
• awx-ui : SUCCESS in 15m 09s
• awx-ui-next : SUCCESS in 15m 19s
• awx-swagger : SUCCESS in 21m 18s
• awx-detect-schema-change : FAILURE in 19m 28s (non-voting)
• awx-ansible-modules : FAILURE in 14m 03s

[AlanCoding]

Well I was able to get this to run with having root privileges, but we don't have that for these tests. Basically we have to have a python3 Ansible virtual environment (a real one, not the hacked one I have used before).

I also suspect that the distributed version of Ansible from the rpm we have in the container just doesn't have the ansible_test package installed. It has the CLI entry point. That leaves me kind of stuck on this error:

Traceback (most recent call last):
  File "/usr/bin/ansible-test", line 28, in <module>
    main()
  File "/usr/bin/ansible-test", line 22, in main
    from ansible_test._internal.cli import main as cli_main
ImportError: No module named ansible_test._internal.cli

This can be remedied by re-installing from git+https://github.com/ansible/ansible.git. That's also not really okay to do, because we're sharing this image with other uses that want to the version of Ansible that would be used in production. So we have to have a different container image for theses tests, or just abandon hope of running them in CI. I could still be wrong about this point.

With a different install of Ansible, I can run the target as it is. Doing that and fixing the errors will turn into the current near-term plan.

[softwarefactory-project-zuul]

Build succeeded.

• awx-api-lint : SUCCESS in 13m 30s
• awx-api : SUCCESS in 19m 59s
• awx-ui : SUCCESS in 16m 32s
• awx-ui-next : SUCCESS in 16m 54s
• awx-swagger : SUCCESS in 19m 42s
• awx-detect-schema-change : FAILURE in 21m 14s (non-voting)
• awx-ansible-modules : SUCCESS in 13m 09s