Bug 1829749

Summary: Ansible jobs fail on a new Satellite 6.7 installation
Product: Red Hat Satellite Reporter: Nagoor Shaik <nshaik>
Component: AnsibleAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED NOTABUG QA Contact: Lukas Pramuk <lpramuk>
Severity: medium Docs Contact:
Priority: high    
Version: 6.7.0Keywords: Triaged
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-01 00:45:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Nagoor Shaik 2020-04-30 09:27:09 UTC 
Description of problem:
Ansible jobs fail on a new Satellite 6.7 installation 

Version-Release number of selected component (if applicable):
Satellite 6.7 GA

How reproducible:
100%

Steps to Reproduce:
1. Install Satellite 6.7
2. Run any Ansible job which would fail

Actual results:
Inspect the /var/log/foreman/production.log, it shows that ansible-runner command is not found.

Expected results:
In Satellite 6.6 ansible-runner was options, but with Satellite 6.7 defaults to ansible-runner as the default option for running Ansible jobs, end-user has to install this package manually.

  # satellite-maintain packages unlock
  # yum install ansible-runner -y
  # satellite-maintain packages lock
 
Now Ansible jobs would run without any issues.

Additional info:

As ansible-runner is the default way for running Ansible jobs, we should create a dependency with the Ansible plugin to install this package automatically.
Comment 3 jcallaha 2020-04-30 15:15:04 UTC 
In our latest 6.7 installer run, I'm seeing runner being installed at the 30% mark. Do you have the installer log from your 6.7 installation?

...
Package[foreman-cli]                               [29%]Installing             File[/etc/hammer/cli.modules.d/foreman.yml]        [29%]Installing             File[/root/.hammer]                                [30%]Installing             File[/root/.hammer/cli.modules.d]                  [30%]Installing             File[/root/.hammer/cli.modules.d/foreman.yml]      [30%]Installing             File[/etc/foreman-proxy/ansible.cfg]               [30%]Installing             File[/usr/share/foreman-proxy/.ansible.cfg]        [30%]Installing             Package[ansible-runner]                            [30%]Installing             Concat_file[/etc/foreman/settings.yaml]            [31%]Installing             Concat_file[/etc/httpd/conf/ports.conf]            [31%]Installing             File[/etc/httpd/conf/httpd.conf]                   [31%]Installing             File[log_config.load]                              [31%]Installing             File[systemd.load]                                 [31%]Installing             File[unixd.load]                                   [31%]Installing          
...
Comment 4 Nagoor Shaik 2020-05-01 00:45:13 UTC 
Apologies,

I was using a old snap, which caused the confusion. I rebuild my Satellite 6.7 with GA repos and can certainly see the ansible-runner package installation

~~~
# grep ansible-runner /var/log/foreman-installer/satellite.log 
[DEBUG 2020-04-29T11:05:58 main]  /Package[ansible-runner]: Provider yum does not support features targetable; not managing attribute command
[ INFO 2020-04-29T11:05:59 main]  MONITOR_RESOURCE Package[ansible-runner]
[ INFO 2020-04-29T11:07:17 main]  /Package[ansible-runner]: Starting to evaluate the resource
[DEBUG 2020-04-29T11:07:17 main]  Executing: '/usr/bin/rpm -q ansible-runner --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n'
[DEBUG 2020-04-29T11:07:17 main]  Executing: '/usr/bin/rpm -q ansible-runner --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n --whatprovides'
[DEBUG 2020-04-29T11:07:17 main]  Package[ansible-runner](provider=yum): Ensuring => present
[DEBUG 2020-04-29T11:07:17 main]  Executing: '/usr/bin/yum -d 0 -e 0 -y install ansible-runner'
[ WARN 2020-04-29T11:07:22 main]  /Stage[main]/Foreman_proxy::Plugin::Ansible::Runner/Package[ansible-runner]/ensure: created
[DEBUG 2020-04-29T11:07:22 main]  /Package[ansible-runner]: The container Class[Foreman_proxy::Plugin::Ansible::Runner] will propagate my refresh event
[ INFO 2020-04-29T11:07:22 main]  /Package[ansible-runner]: Evaluated in 5.54 seconds
~~~

I will close this bug request.