Version-Release number of selected component (if applicable): 5.8.0.14-rc3.20170509175238_5dbf87a How reproducible: Always Steps to Reproduce: 1. Use podified CFME. 2. Enable Embedded Ansible role. Actual results: Embedded Ansible role is not enabled. Expected results: Embedded Ansible role should be enabled. Additional info: [----] E, [2017-05-10T12:37:02.933423 #356:b05ce80] ERROR -- : AwesomeSpawn: ansible-tower-setup exit code: 2 [----] E, [2017-05-10T12:37:02.933510 #356:b05ce80] ERROR -- : AwesomeSpawn: /var/lib/awx/setup/setup.sh: line 333: sudo: command not found [----] E, [2017-05-10T12:37:02.933741 #356:b05ce80] ERROR -- : [AwesomeSpawn::CommandResultError]: ansible-tower-setup exit code: 2 Method:[rescue in do_before_work_loop] [----] E, [2017-05-10T12:42:42.313053 #356:f3f3cc] ERROR -- : /opt/rh/cfme-gemset/gems/awesome_spawn-1.4.1/lib/awesome_spawn.rb:105:in `run!' /var/www/miq/vmdb/lib/embedded_ansible.rb:102:in `block in run_setup_script' /var/www/miq/vmdb/lib/embedded_ansible.rb:112:in `with_inventory_file' /var/www/miq/vmdb/lib/embedded_ansible.rb:95:in `run_setup_script' /var/www/miq/vmdb/lib/embedded_ansible.rb:54:in `start' /var/www/miq/vmdb/app/models/embedded_ansible_worker/runner.rb:37:in `setup_ansible' /var/www/miq/vmdb/app/models/embedded_ansible_worker/runner.rb:13:in `do_before_work_loop' /var/www/miq/vmdb/app/models/embedded_ansible_worker/runner.rb:7:in `prepare' /var/www/miq/vmdb/app/models/miq_worker/runner.rb:129:in `start' /var/www/miq/vmdb/app/models/miq_worker/runner.rb:21:in `start_worker' /var/www/miq/vmdb/app/models/embedded_ansible_worker.rb:10:in `block in start_runner'
This is resolved as of https://github.com/ManageIQ/manageiq-pods/pull/163
Putting back to ON_DEV as separate change is needed for downstream.
Verified in 5.9.0.4.20171024163837_ef71ea6 I see some messages the following [----] I, [2017-10-31T16:06:14.505887 #7:88e0ec4] INFO -- : MIQ(EmbeddedAnsible.container_start) Waiting for Ansible co ntainer to respond However, Embedded Ansible role is enabled in UI w/o issues.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0382