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.
1. Proposed title of this feature request
Allow user to choose between Graphical and Text mode anaconda installer during system build via Satellite 6
2. What is the nature and description of the request?
Modification of the code shipped in provisioning templates to allow access of Graphical or Text mode anaconda console based on host parameter passed.
3. Why does the customer need this? (List the business requirements here)
By default we have "skipx" used in the provisioning templates shipped with Satellite and hence during the system build, everything happens in text mode.
Under certain circumstances e.g. Disk layout verification failure, One might be interested in mitigating the same manually by accessing the Graphical console of the anaconda installer and manually fixing the layout issues at runtime.
4. How would the customer like to achieve this? (List the functional requirements here)
There should be a host\hostgroup\global parameter present e.g. use_graphical_installer, using which, one can decide whether the kickstart should happen in text mode ( skipx ) or in graphical mode ( graphical).
5. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
* Install Satellite and prepare it for system deployments.
* Create a host with a parameter with the name "use_graphical_installer" and value "true" and submit the build of the host.
* Observe if the Graphical Anaconda installer is visible and the system build completes fine or not.
6. Is there already an existing RFE upstream or in Red Hat Bugzilla?
Feature #35177: Add option to permit graphical installs for Red Hat - Foreman
https://projects.theforeman.org/issues/35177
Fixes #35177 - Option to switch to graphical kickstart by jcpunk ? Pull Request #9291 ? theforeman/foreman
https://github.com/theforeman/foreman/pull/9291/files
7. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
As soon as possible
8. Is the sales team involved in this request and do they have any additional input?
NA
9. List any affected packages or components.
foreman
10. Would the customer be able to assist in testing this functionality if implemented?
Yes
11. Additional information:
NA
Verified.
Tested on Satellite 6.13.0 Snap 4.0
Steps followed:
1. Created a new host with `use_graphical_installer` param set to true
2. Created a VM with the same MAC address of that host
3. Started the VM
Observation:
the graphical anaconda installer interface was shown
In addition, when setting the `use_graphical_installer` param set to false,
the anaconda installer was running in text mode.
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.13 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-2023:2097