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.
"After first logging in to the website you are presented with this sentences:
Before you can use Satellite 6 for the first time there are a few tasks that must be performed. You must decide how you wish to use the software, and update the primary settings file config/settings.yaml and the settings to indicate your selections.
The "config/settings.yaml" is not a link, but the word "settings" immediately following it is. Does that link take you to the "config/settings.yaml"? Because the way it's worded makes them sound like separate entities. And there isn't any information on the page nor the Provisioning Guide about where the "config/settings.yaml" is located."
Based on this comment from the Provisioning Guide announcement. https://access.redhat.com/discussions/1294043
Assigning to Ali for review.
Ali - if memory serves, config/settings.yaml is a general configuration file that exists on your Satellite Server that allows you to set various options.
We might need to check with Adam Currier if editing this file is supported, and if so, some common options. If not, a note telling customers that they may see this screen when they first log in, but that it is just a default notice, for example.
This belongs in the Host Configuration Guide now for 6.2 and is already partially described. I added a line to section 8.2 Global Parameters stating that "You should not manually change the `/etc/foreman/settings.yaml` configuration file because they are overwritten the next time you run the `satellite-installer` command."
The pop-up message referenced in the description no longer appears in 6.2.
It's also already called out in section 11.3 for remote execution.