Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
I was trying upgrade from 6.1.11 -> 6.2.5 and installer failed at db migrate step due to known issue. Later after applying fix, when I re-run the installer from "/user/share/foreman" I got:
[root@cloud-qe-22 foreman]# satellite-installer --upgrade
ERROR: No installation scenario was selected, the installer can not continue.
Even --help content is dependent on selected scenario.
Select scenario with --scenario SCENARIO or list available scenarios with --list-scenarios.
[root@cloud-qe-22 foreman]# satellite-installer --scenario satellite --upgrade
ERROR: Scenario (config/satellite.yaml) was not found, can not continue
Version-Release number of selected component (if applicable):
However if I ran the installer from $HOME then, it was executed successfully.
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
installer failed if run from /usr/share/foreman
Expected results:
user should be able to run installer from anywhere
Additional info:
[root@qe-sat6 ~]# cd /usr/share/foreman
[root@qe-sat6 foreman]# satellite-installer --help | grep tftp
--foreman-plugin-discovery-tftp-root TFTP root to install image into (current: "/var/lib/tftpboot")
--foreman-proxy-tftp Enable TFTP feature (current: true)
VERIFIED with sat6.3.0 snap13.0
Comment 5Satellite Program
2018-02-21 16:51:07 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/RHSA-2018:0336
Description of problem: I was trying upgrade from 6.1.11 -> 6.2.5 and installer failed at db migrate step due to known issue. Later after applying fix, when I re-run the installer from "/user/share/foreman" I got: [root@cloud-qe-22 foreman]# satellite-installer --upgrade ERROR: No installation scenario was selected, the installer can not continue. Even --help content is dependent on selected scenario. Select scenario with --scenario SCENARIO or list available scenarios with --list-scenarios. [root@cloud-qe-22 foreman]# satellite-installer --scenario satellite --upgrade ERROR: Scenario (config/satellite.yaml) was not found, can not continue Version-Release number of selected component (if applicable): However if I ran the installer from $HOME then, it was executed successfully. How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: installer failed if run from /usr/share/foreman Expected results: user should be able to run installer from anywhere Additional info: