Description of problem: Leapp upgrades of Ansible Tower result in Ansible Tower failing to start/connect. According to this KCS, it's unsupported. https://access.redhat.com/articles/2360841 Version-Release number of selected component (if applicable): RHEL 7 > RHEL 8 Expected results: Leapp should inhibit the upgrade of Ansible Tower. The documentation should also list that Ansible Tower is not supported. This should not just be in a kcs. Additional info:
Hi John, thanks for the report. Is the KCS link correct? I haven't found anything about ansible tower inside and the doc is speaking about conversions, not upgrades.
Bah. thats the wrong link. My apologies [How do I migrate my Ansible Tower installation from RHEL7 to RHEL8 ? - Red Hat Customer Portal](https://access.redhat.com/solutions/5994961)
Thanks! It's clear now.
Amendment: Leapp should prohibit any Ansible products.
As asked by Martin Kluson in an email thread > We are not sure what is the best way how to reliably detect that Ansible Tower is installed. Answer: * To detect if Ansible Tower (or Controller by its new name) is installed, a simple test rpm -q automation-controller or rpm -q ansible-tower will tell you * To detect if Ansible Tower (or Controller by its new name) is running, a simple test systemctl status automation-controller or systemctl status ansible-tower will tell you