Bug 1840723
| Summary: | Selected scenario is DISABLED, can not continue | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Lukáš Hellebrandt <lhellebr> |
| Component: | Installation | Assignee: | Evgeni Golov <egolov> |
| Status: | CLOSED ERRATA | QA Contact: | Lukáš Hellebrandt <lhellebr> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.8.0 | CC: | aruzicka, egolov, inecas, swadeley, zhunting |
| Target Milestone: | 6.8.0 | Keywords: | AutomationBlocker, PrioBumpQA, Regression, Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | satellite-installer-6.8.0.7-1 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-10-27 13:02:46 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: | |||
*** Bug 1841908 has been marked as a duplicate of this bug. *** Hello Problem still exists in Snap 4 [root@dell-r330-12 ~]# rpm -q satellite satellite-6.8.0-0.4.beta.el7sat.noarch [root@dell-r330-12 ~]# rpm -q foreman-installer foreman-installer-2.1.0-0.3.1.rc2.el7sat.noarch Verified with Sat 6.8 snap 7.0. Succesfully installed Capsule using command provided by 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 (Important: Satellite 6.8 release), 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-2020:4366 |
Description of problem: After running capsule-certs-generate on Satellite, I get a command as a result that I'm supposed to run. Running this command on the proxy-to-be causes error: ``` ERROR: Selected scenario is DISABLED, can not continue. Use --list-scenarios to list available options. You can also --enable-scenario SCENARIO to make the selected scenario available. ``` The command is: ``` foreman-installer --scenario foreman-proxy-content --certs-tar-file "/root/capsule_certs.tar" --foreman-proxy-content-parent-fqdn "<SATELLITE-FQDN>" --foreman-proxy-register-in-foreman "true" --foreman-proxy-foreman-base-url "https://<SATELLITE-FQDN>" --foreman-proxy-trusted-hosts "<SATELLITE-FQDN>" --foreman-proxy-trusted-hosts "<CAPSULE-FQDN>" --foreman-proxy-oauth-consumer-key "xSsj4wUK8LfdsLerM45bfRSEsGFwCVbw" --foreman-proxy-oauth-consumer-secret "v79DiokALheRjWMohm3WVeKVjf5CABJS" --puppet-server-foreman-url "https://<SATELLITE-FQDN>" ``` Fishy parts are "foreman-installer" and "foreman-proxy-content". This is confirmed by "--list-scenarios" which returns: ``` Available scenarios Capsule (use: --scenario capsule) Install a stand-alone Satellite Capsule. Satellite (use: --scenario satellite) Install Satellite server ``` Version-Release number of selected component (if applicable): Sat+Capsule 6.8 snap 1.0 How reproducible: Deterministic Steps to Reproduce: 1. On Satellite, run capsule-certs-generate (according to Installing Capsule Server docs) 2. On Capsule, run the command that you get from 1) Actual results: ERROR: Selected scenario is DISABLED, can not continue. Expected results: Successfull Capsule installation