Bug 1740740 - [RFE] Add the whiptail command to the kickstart environment for RHEL 8.
Summary: [RFE] Add the whiptail command to the kickstart environment for RHEL 8.
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: lorax-templates-rhel
Version: 8.2
Hardware: All
OS: All
Target Milestone: rc
: 8.0
Assignee: Brian Lane
QA Contact: Release Test Team
Depends On:
TreeView+ depends on / blocked
Reported: 2019-08-13 15:03 UTC by jcastran
Modified: 2019-08-14 22:19 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-08-13 16:43:44 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

Description jcastran 2019-08-13 15:03:41 UTC
1. Proposed title of this feature request

Add the whiptail command to the kickstart environment for RHEL 8.

3. What is the nature and description of the request?
Add the newt package to the kickstart environment for RHEL 8. We use the whiptail command to generate user dialog boxes and prompt for input during semi-automated kickstart installs. This has worked well for us in RHEL 7, but I find that the newt package and whiptail command are no longer in the kickstart environment as of RHEL 8.

4. Why does the customer need this? (List the business requirements here)
to generate user dialog boxes and prompt for input during semi-automated kickstart installs

5. How would the customer like to achieve this? (List the functional requirements here)
Add the whiptail command to the installation environment

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
We can test this

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?

8. Does the customer have any specific time-line dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?

9. Is the sales team involved in this request and do they have any additional input?

10. List any affected packages or components.

11. Would the customer be able to assist in testing this functionality if implemented?

Comment 2 Samantha N. Bueno 2019-08-13 16:43:44 UTC
This is out of scope for what we support in kickstart and would add a considerable support/maintenance burden that engineering can not sustain.

I would like to understand the need for this, however, and perhaps we can make changes to kickstart which would render this unnecessary:
- Why is it necessary to pop up dialog boxes prompting for input? As opposed to, say, having a partially filled kickstart and letting the installer halt once it processes the ks file and displays the error/warning messages on the spoke statuses.
- What information is being requested from users during kickstart? (If it is something generic enough, perhaps this is a need we can address that would satisfy other customers as well, for example.)

I'm going to close this bug since we are not going to add the requested support (which is what this bug is specifically about), but we can continue our discussion (emails will still be sent to me and anyone else Cc'ed on it).

Comment 3 Martin Kolman 2019-08-14 10:06:38 UTC
Also, if user interaction during installation is really needed & very specific to the needs of the customer, there is the option to deploy a custom Anaconda Addon[0][1]. Addons are the proper way to gather information from users during the installation, can run in GUI/TUI or both, can be configured via kickstart through their own section as well as to run arbitrary tasks at install time.

[0] https://rhinstaller.github.io/anaconda-addon-development-guide/
[1] https://github.com/rhinstaller/hello-world-anaconda-addon/tree/rhel-8

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