Bug 1840723 - Selected scenario is DISABLED, can not continue
Summary: Selected scenario is DISABLED, can not continue
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.8.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: 6.8.0
Assignee: Evgeni Golov
QA Contact: Lukáš Hellebrandt
URL:
Whiteboard:
: 1841908 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-27 13:44 UTC by Lukáš Hellebrandt
Modified: 2020-10-27 13:02 UTC (History)
5 users (show)

Fixed In Version: satellite-installer-6.8.0.7-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 13:02:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:4366 0 None None None 2020-10-27 13:02:57 UTC

Description Lukáš Hellebrandt 2020-05-27 13:44:48 UTC
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

Comment 2 Brad Buckingham 2020-06-01 14:29:24 UTC
*** Bug 1841908 has been marked as a duplicate of this bug. ***

Comment 3 Stephen Wadeley 2020-06-11 07:44:04 UTC
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

Comment 5 Lukáš Hellebrandt 2020-07-02 15:47:20 UTC
Verified with Sat 6.8 snap 7.0. Succesfully installed Capsule using command provided by Satellite.

Comment 8 errata-xmlrpc 2020-10-27 13:02:46 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 (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


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