Bug 1599995 - Capsule scenario should also install rubygem-smart_proxy_ansible
Summary: Capsule scenario should also install rubygem-smart_proxy_ansible
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.4.0
Assignee: satellite6-bugs
QA Contact: Peter Ondrejka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-11 07:35 UTC by sbadhwar
Modified: 2019-11-05 23:28 UTC (History)
3 users (show)

Fixed In Version: satellite-installer-6.4.0.6-1.beta
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-16 19:28:15 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description sbadhwar 2018-07-11 07:35:35 UTC
Description of problem:
Currently, the satellite-installer --scenario capsule does not install rubygem-smart_proxy_ansible which might be required for running Ansible based Jobs on a default installation of Satellite.

Not having the gem installed causes the job execution raises an error.


Version-Release number of selected component (if applicable):
Satellite 6.4 Snap 10

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:
Ansible execution fails on a default install of Capsule executed using
satellite-installer --scenario capsule

Expected results:
Ansible job execution should work fine and rubygem-smart_proxy_ansible is installed by the default installation


Additional info:

Comment 4 Peter Ondrejka 2018-07-23 10:23:17 UTC
Verified with satellite 6.4 snap 13 capsule, 
rubygem-smart_proxy_ansible-2.0.2-3.el7sat.noarch
tfm-rubygem-foreman_ansible_core-2.1.1-1.el7sat.noarch
get installed with capsule

Comment 5 Bryan Kearney 2018-10-16 19:28:15 UTC
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/RHSA-2018:2927


Note You need to log in before you can comment on or make changes to this bug.