MrMEEE / awx-rpm-v2

AWX-RPM Reignited
GNU Affero General Public License v3.0
36 stars 11 forks source link

AWX-RPM install on RHEL9 #3

Closed apoorvp2 closed 1 year ago

apoorvp2 commented 1 year ago

Hi , While installing the latest AWX-rpm from the awx-rpm-install.yml there is an issue arising related to the package python3-readme-renderer = 37.3 .Below is the error returned : -

"Depsolve Error occurred: \n Problem: package awx-rpm-21.11.0-11.el9.x86_64 requires python3-readme-renderer = 37.3, but none of the providers can be installed\n - cannot install the best candidate for the job\n - nothing provides python3.9dist(bleach) >= 2.1 needed by python3-readme-renderer-37.3-1.el9.noarch".

I have not found a relevant source for the package provides python3.9dist(bleach) . Pls suggest possible resolution for the above issue.

MrMEEE commented 1 year ago

Hi

Are you running on CentOS or RHEL?

MrMEEE commented 1 year ago

Just noticed the description.. Forget the question above

The python3-bleach package comes from the pypi copr repo, which should be enabled earlier in the playbook?

What does a

dnf whatprovides python3-bleach

show?

MrMEEE commented 1 year ago

Should return:

[root@awx-test-vm ~]# dnf whatprovides python3-bleach
Updating Subscription Management repositories.
Last metadata expiration check: 0:04:47 ago on 2023-04-25T23:27:39 CEST.
python3-bleach-6.0.0-1.el9.noarch : An easy safelist-based HTML-sanitizing tool.
Repo        : copr:copr.fedorainfracloud.org:group_copr:PyPI
Matched from:
Provide    : python3-bleach = 6.0.0-1.el9
apoorvp2 commented 1 year ago

Hi Martin,

Thanks for the suggestion . I was able to install python3-bleach.

But there seems a catch as the AWX-RPM repository & the pypi copr repo cannnot stay enabled together simultaneously as its producing python package conflicts like mentioned below : -

"fatal: [localhost]: FAILED! => {"changed": false, "failures": [], "msg": "Unknown Error occurred: Transaction test error:\n file /usr/lib64/python3.9/site-packages/PyYAML-6.0.dist-info/METADATA conflicts between attempted installs of python3-pyyaml-6.0-1.el9.noarch and python3-PyYAML-6.0-1.el9.noarch\n"

PFA the snippets as there are many such package conflicts. I tried disbaling the pypi copr repo and continue with the install to avoid conflict but again the step at AWX-RPM install fails with a dependency package python3-coreapi whose repo source again lies at the disabled pypi copr repo. It is leading to a lot of back and forth manual repo enables/disables.

I would appreciate your inputs on the above scenario.

MrMEEE commented 1 year ago

Is this when you try to update, or under installation??

I don't have any issues to install AWX-RPM.. but I do get package conflicts on updates..

The only way to avoid this (as I see it), is to compile all the packages that I'm using from the PYPI, and that might be a solution in the future, but for now it's not..

To update, try running "dnf update --nobest"

apoorvp2 commented 1 year ago

Hi ,

The above issue of package conflicts was coming up during the installation. Also , I found out that ansible-core [ansible cli] and the AWX-RPM has a conflict on the PyYaml version during the installation. Finally I was able to run the complete setup and AWX Console is up and running.

I tested out normal playbook executions and it went fine.One feature that seems missing in the AWX console with the RPM set up is "Install Bundle" feature while adding a new Execution node [Previously known as Isolated Node in Ansible Tower] .This feature is available in the enterprise versions and also the kubernetes based version of AWX 21.11 .

Pls suggest a possible way to enable execution node in the current setup.

PFA the snippets attached.

image image

MrMEEE commented 1 year ago

Yeah, I have never testet having ansible on the AWX server.. might be able to fix the that dependency in time..

I have created an issue, #5, which I will return to, when the autobuilds are rolling..