Description of problem:
Unable to enable foreman_discovery_smart_proxy using Capsule scenario
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. satellite-installer -S capsule -h | grep discovery
Above should return discovery_smart_proxy installer options
Above to return discovery_smart_proxy installer options
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/17926 has been resolved.
*** Bug 1333039 has been marked as a duplicate of this bug. ***
That looks like the satellite scenario? It should be capusle. The method looks good though.
Version Tested: Satellite-6.3 Snap 18
It is possible to enable foreman_discovery_smart_proxy using Capsule scenario
# satellite-installer -S capsule -h|grep discovery
--[no-]enable-foreman-proxy-plugin-discovery Enable 'foreman_proxy_plugin_discovery' puppet module (default: false)
= Module foreman_proxy_plugin_discovery:
--foreman-proxy-plugin-discovery-image-name tarball with images (current: "fdi-image-latest.tar")
--foreman-proxy-plugin-discovery-install-images should the discovery image be downloaded and extracted (current: false)
--foreman-proxy-plugin-discovery-source-url source URL to download from (current: "http://downloads.theforeman.org/discovery/releases/latest/")
--foreman-proxy-plugin-discovery-tftp-root tftp root to install image into (current: "/var/lib/tftpboot")
[root@ibm-x3650m4-01-vm-01 ~]# rpm -qa|grep satellite
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.