Bug 1318538 - smart_proxy_discovery and hammer_cli_foreman_discovery packages should be installed default with installer
Summary: smart_proxy_discovery and hammer_cli_foreman_discovery packages should be ins...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Martin Bacovsky
QA Contact: Sachin Ghai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-17 07:48 UTC by Sachin Ghai
Modified: 2019-06-13 21:25 UTC (History)
7 users (show)

Fixed In Version: satellite-installer-6.2.0.12-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-14 20:59:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1885 0 normal SHIPPED_LIVE Satellite 6.2.2 bug fix update 2016-09-15 00:57:56 UTC

Description Sachin Ghai 2016-03-17 07:48:21 UTC
Description of problem: Currently with sat6.2 snap3 installer installs only below package.

]# rpm -qa | grep discovery
tfm-rubygem-foreman_discovery-5.0.0.1-1.el7sat.noarch

However, following packages should be auto installed with installer

rubygem-smart_proxy_discovery-
rubygem-hammer_cli_foreman_discovery


Version-Release number of selected component (if applicable):
Sat6.2 snap3

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
sat6.2 snap3 installer installs only tfm-rubygem-foreman_discovery package. It doesn't install smart_proxy_discovery and cli_foreman_discovery

Expected results:
smart_proxy_discovery and cli_foreman_discovery should be installed with installer.

Additional info:

Comment 4 Lukas Zapletal 2016-04-18 14:01:03 UTC
This has always been issue downstream, hopefully scenarios will solve this forever.

Comment 8 Martin Bacovsky 2016-08-09 14:53:18 UTC
I've added migration that enables optins for the discovery plugin to foreman proxy. This allows installer to install the plugin and its dependences.

To test you should see the installer options:

[root@sat-rhel7 ~]# satellite-installer --scenario satellite --help |grep discovery
    --[no-]enable-foreman-plugin-discovery Enable 'foreman_plugin_discovery' puppet module (default: true)
    --[no-]enable-foreman-proxy-plugin-discovery Enable 'foreman_proxy_plugin_discovery' puppet module (default: true)
= Module foreman_plugin_discovery:
    --foreman-plugin-discovery-image-name  tarball with images (default: "fdi-image-latest.tar")
    --foreman-plugin-discovery-install-images  should the installer download and setup discovery images
    --foreman-plugin-discovery-source-url  source URL to download from (default: "http://downloads.theforeman.org/discovery/releases/latest/")
    --foreman-plugin-discovery-tftp-root  tftp root to install image into (default: "/var/lib/tftpboot")
= Module foreman_proxy_plugin_discovery:
    --foreman-proxy-plugin-discovery-image-name  tarball with images (default: "fdi-image-latest.tar")
    --foreman-proxy-plugin-discovery-install-images  should the discovery image be downloaded and extracted (default: false)
    --foreman-proxy-plugin-discovery-source-url  source URL to download from (default: "http://downloads.theforeman.org/discovery/releases/latest/")
    --foreman-proxy-plugin-discovery-tftp-root  tftp root to install image into (default: "/var/lib/tftpboot")

and installed dependences after the installer run:

[root@sat-rhel7 ~]# rpm -qa|grep discovery
tfm-rubygem-hammer_cli_foreman_discovery-0.0.2.3-1.el7sat.noarch
tfm-rubygem-foreman_discovery-5.0.0.8-1.el7sat.noarch
rubygem-smart_proxy_discovery-1.0.3-3.el7sat.noarch

Comment 9 Sachin Ghai 2016-09-02 10:20:22 UTC
Verified with satellite 6.2.2 Snap 1.0

I can see installed discovery packages with installer.

 ~]# satellite-installer --scenario satellite --foreman-admin-password changeme
Installing             Done                                               [100%] [..................................................................]
  Success!
  * Satellite is running at https://qebladexx.xx.xx.redhat.com
      Initial credentials are admin / changeme
  * To install additional capsule on separate machine continue by running:

      capsule-certs-generate --capsule-fqdn "$CAPSULE" --certs-tar "~/$CAPSULE-certs.tar"

  The full log is at /var/log/foreman-installer/satellite.log
[root@qeblade36 ~]# rpm -qa | grep discovery
tfm-rubygem-foreman_discovery-5.0.0.9-1.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_discovery-0.0.2.3-1.el7sat.noarch
rubygem-smart_proxy_discovery-1.0.3-3.el7sat.noarch



~]# satellite-installer --scenario satellite --help |grep discovery

    --[no-]enable-foreman-plugin-discovery Enable 'foreman_plugin_discovery' puppet module (default: true)
    --[no-]enable-foreman-proxy-plugin-discovery Enable 'foreman_proxy_plugin_discovery' puppet module (default: true)
= Module foreman_plugin_discovery:
    --foreman-plugin-discovery-image-name  tarball with images (default: "fdi-image-latest.tar")
    --foreman-plugin-discovery-install-images  should the installer download and setup discovery images
    --foreman-plugin-discovery-source-url  source URL to download from (default: "http://downloads.theforeman.org/discovery/releases/latest/")
    --foreman-plugin-discovery-tftp-root  tftp root to install image into (default: "/var/lib/tftpboot")
= Module foreman_proxy_plugin_discovery:
    --foreman-proxy-plugin-discovery-image-name  tarball with images (default: "fdi-image-latest.tar")
    --foreman-proxy-plugin-discovery-install-images  should the discovery image be downloaded and extracted (default: false)
    --foreman-proxy-plugin-discovery-source-url  source URL to download from (default: "http://downloads.theforeman.org/discovery/releases/latest/")
    --foreman-proxy-plugin-discovery-tftp-root  tftp root to install image into (default: "/var/lib/tftpboot")

Comment 11 errata-xmlrpc 2016-09-14 20:59:59 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/RHBA-2016:1885


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