Ansible with ManageIQ

Support
#1

I wanted to know if we could use ansible playbooks on manageIQ without having tower? I have activated embedded ansible and i can see the services running in the server by roles tab, however i cannot see a worker in the diagnostic server. Also GIT configuration etc looks greyed out

Anyone has prior experience like this and can help

#2

When you enable the Embedded Ansible Role in MIQ, it does install a “headless” version of Ansible Tower in the background. You can try checking if you can any log files in /var/log/tower

#3

I can see some logs in /var/log/manageiq/production.log
production.log:[----] I, [2018-10-09T04:46:53.347051 #8496:b83cd58] INFO – : [ ActionCable] Broadcasting to notifications_1: {:level=>“info”, :created_at=>Tue, 09 Oct 2018 08:46:53 UTC +00:00, :text=>“The role %{role_name} has started acti vation on server %{server_name}”, :bindings=>{:role_name=>{:text=>“Embedded Ansi ble”}, :server_name=>{:text=>“XXX”}}}

#4

Also when i search for file called tower i do find something

[root@host-10-73-123-4 manageiq]# find / -name tower*
/usr/local/lib/ruby/gems/2.3.0/bundler/gems/manageiq-providers-ansible_tower-fcb960cfdad9/app/models/manageiq/providers/ansible_tower/shared/automation_manager/tower_api.rb

#5

This is an openstack appliance i have setup but i cannot find any ansible or tower rpm
[root@host manageiq]# rpm -q --all | grep -i ansible
[root@host manageiq]# rpm -q --all | grep -i tower

#6

We do have some tower RPMs installed on out Ansible Node.I guess the installation did not work in our case (I have not installed our Embedded Ansible Appliance, therefore I have no idea how to do it)

rpm -qa |grep tower
ansible-tower-server-3.2.5-1.el7at.x86_64
ansible-tower-venv-tower-3.2.5-1.el7at.x86_64
ansible-tower-venv-ansible-3.2.5-1.el7at.x86_64
ansible-tower-setup-3.2.5-1.el7at.x86_64
#7

Are you running ManageIQ or CloudForms?

Make sure your appliance has enough memory, you want about 12GB as an absolute minimum for the embedded Tower/AWX installation to start. Embedded Ansible features being greyed out is an indication that the AWX installation has not completed yet (or failed).

There are some troubleshooting tips here: https://manageiq.gitbook.io/mastering-cloudforms-automation-addendum/embedded_ansible/chapter-10

pemcg

#8

I dont see any distress for resource, looks quite ok to me.

top - 01:41:33 up 2 days, 58 min, 1 user, load average: 0.48, 0.52, 0.51
Tasks: 332 total, 3 running, 329 sleeping, 0 stopped, 0 zombie
%Cpu(s): 4.2 us, 0.7 sy, 0.1 ni, 94.6 id, 0.1 wa, 0.0 hi, 0.3 si, 0.0 st
KiB Mem : 20393688 total, 6947684 free, 9827232 used, 3618772 buff/cache
KiB Swap: 6287356 total, 6287356 free, 0 used. 9912592 avail Mem

#9

I think this has something to do with embedded docker, i have a broken dns and public internet, i think ansible requires it for setup. I saw some logs as below
Oct 10 05:15:23 host- dockerd-current: time=“2018-10-10T05:15:23.783770759-04:00” level=warning msg=“Error getting v2 registry: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on X.X.X.X:53: server misbehaving”
Oct 10 05:15:23 host-dockerd-current: time=“2018-10-10T05:15:23.783844170-04:00” level=error msg=“Attempting next endpoint for pull after error: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on X.X.X.Y:53: server misbehaving”

#10

I was right, the ansible engine (not tower) downloads the following docker containers at run time,
rabbitmq:3
memcached
awx_web
awx_task
Alpine
Since i had a broken DNS and internet it was not starting. I imported these from a tar file into docker daemon after manually starting the docker daemon, and now it seems to have started the ansible worker. I will do some further testing tomorrow. My suggestion is to have these containers presaved on the appliance unless someone knows there is a reason this approach was not taken. At run time, latest pull can be tried which will upgrade but it will run at least a base version