Description of problem: While installing external capsule, the installer failed w/ error: Scenario (/etc/foreman-installer/scenarios.d/foreman-proxy-content.yaml) was not found. though the above file exists. The capsule-cert generate provides the installer command w/ option --scenario foreman-proxy-content, however installer cmd list following scenarios: Capsule (use: --scenario capsule) Install a stand-alone Satellite capsule Satellite (INSTALLED) Install Satellite server Version-Release number of selected component (if applicable): sat6.3 beta snap1 How reproducible: Steps to Reproduce: 1. run the cmd generated from capsule-cert-generate as below w/ other required options satellite-installer --scenario foreman-proxy-content 2. 3. Actual results: ERROR: Scenario (/etc/foreman-installer/scenarios.d/foreman-proxy-content.yaml) was not found, can not continue Expected results: installer should succeed Additional info:
Environment: * candlepin-2.0.35-1.el7.noarch * candlepin-selinux-2.0.35-1.el7.noarch * foreman-1.15.0-1.el7sat.noarch * foreman-cli-1.15.0-1.el7sat.noarch * foreman-compute-1.15.0-1.el7sat.noarch * foreman-debug-1.15.0-1.el7sat.noarch * foreman-discovery-image-3.1.1-22.el7sat.noarch * foreman-ec2-1.15.0-1.el7sat.noarch * foreman-gce-1.15.0-1.el7sat.noarch * foreman-installer-1.15.0-1.el7sat.noarch * foreman-installer-katello-3.4.0.1-1.el7sat.noarch * foreman-libvirt-1.15.0-1.el7sat.noarch * foreman-openstack-1.15.0-1.el7sat.noarch * foreman-ovirt-1.15.0-1.el7sat.noarch * foreman-postgresql-1.15.0-1.el7sat.noarch * foreman-proxy-1.15.0-2.el7sat.noarch * foreman-rackspace-1.15.0-1.el7sat.noarch * foreman-selinux-1.15.0-1.el7sat.noarch * foreman-vmware-1.15.0-1.el7sat.noarch * katello-3.4.0-3.el7sat.noarch * katello-ca-consumer-sat-r220-02.lab.eng.rdu2.redhat.com-1.0-1.noarch * katello-certs-tools-2.4.0-1.el7sat.noarch * katello-client-bootstrap-1.3.0-1.el7sat.noarch * katello-common-3.4.0-3.el7sat.noarch * katello-debug-3.4.0-3.el7sat.noarch * katello-default-ca-1.0-1.noarch * katello-installer-base-3.4.0.1-1.el7sat.noarch * katello-selinux-3.0.2-1.el7sat.noarch * katello-server-ca-1.0-1.noarch * katello-service-3.4.0-3.el7sat.noarch * openldap-2.4.40-13.el7.x86_64 * pulp-client-1.0-1.noarch * pulp-docker-plugins-2.3.0-1.el7sat.noarch * pulp-katello-1.0.2-1.el7sat.noarch * pulp-ostree-plugins-1.2.1-1.el7sat.noarch * pulp-puppet-plugins-2.12.2-1.el7sat.noarch * pulp-puppet-tools-2.12.2-1.el7sat.noarch * pulp-rpm-plugins-2.12.2-1.el7sat.noarch * pulp-selinux-2.12.2-1.el7sat.noarch * pulp-server-2.12.2-1.el7sat.noarch * python-ldap-2.4.15-2.el7.x86_64 * tfm-rubygem-ldap_fluff-0.4.6-1.el7sat.noarch * tfm-rubygem-net-ldap-0.15.0-1.el7sat.noarch
*** Bug 1470679 has been marked as a duplicate of this bug. ***
*** Bug 1482009 has been marked as a duplicate of this bug. ***
*** Bug 1489129 has been marked as a duplicate of this bug. ***
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/21078 has been resolved.
*** Bug 1500521 has been marked as a duplicate of this bug. ***
VERIFIED. @satellite-6.3.0-19.0.beta.el7sat.noarch satellite-installer-6.3.0.6-1.beta.el7sat.noarch by following manual reproducer: # capsule-certs-generate --foreman-proxy-fqdn capsule.example.com --certs-tar /root/capsule.example.com.tar Installing Done [100%] [.....................................] Success! To finish the installation, follow these steps: If you do not have the Capsule registered to the Satellite instance, then please do the following: 1. yum -y localinstall http://satellite.example.com/pub/katello-ca-consumer-latest.noarch.rpm 2. subscription-manager register --org "Default_Organization" Once this is completed run the steps below to start the Capsule installation: 1. Ensure that the satellite-capsule package is installed on the system. 2. Copy the following file /root/capsule.example.com.tar to the system capsule.example.com at the following location /root/capsule.example.com.tar scp /root/capsule.example.com.tar root.com:/root/capsule.example.com.tar 3. Run the following commands on the Capsule (possibly with the customized parameters, see satellite-installer --scenario capsule --help and documentation for more info on setting up additional services): satellite-installer --scenario capsule\ --foreman-proxy-content-parent-fqdn "satellite.example.com"\ --foreman-proxy-register-in-foreman "true"\ --foreman-proxy-foreman-base-url "https://satellite.example.com"\ --foreman-proxy-trusted-hosts "satellite.example.com"\ --foreman-proxy-trusted-hosts "capsule.example.com"\ --foreman-proxy-oauth-consumer-key "ZRyPiHgyisUjmmfrvYsH3ucoLR4ow9bK"\ --foreman-proxy-oauth-consumer-secret "DM9ia9H5xY2mYKbXpTcHPa3nD4c2pV6c"\ --foreman-proxy-content-pulp-oauth-secret "6NNs7ZV2HDo4RuxuZxiHhV9d34QeSqzJ"\ --foreman-proxy-content-certs-tar "/root/capsule.example.com.tar"\ --puppet-server-foreman-url "https://satellite.example.com" The full log is at /var/log/foreman-proxy-certs-generate.log >>> capsule-certs-generate offers correct scenario to install capsule "satellite-installer --scenario capsule\"
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:0336