-
Feature Request
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
None
-
Product / Portfolio Work
-
None
-
False
-
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
-
None
1. Proposed title of this feature request
Enhance openshift-install create ignition-configs & wait for bootstrap-complete Command to Provide Contextual Next-Step Instructions.
2. What is the nature and description of the request?
Currently, after running the openshift-install create ignition-configs command, the CLI output ends abruptly after confirming that the Ignition configs have been created. This may leave end users uncertain about the next steps in the installation process.
Proposed Enhancement:
Modify the command output to include contextual, user-friendly guidance on the next recommended commands — such as waiting for bootstrap completion and proceeding with installation verification.
Example — Current Output:
~~~
[root@vm-232-139 upi]# openshift-install create ignition-configs
INFO Consuming Install Config from target directory
INFO Credentials loaded from the "default" profile in file "/root/.aws/credentials"
INFO Ignition-Configs created in: . and auth
[root@vm-232-139 upi]#
~~~
Example — Proposed Output:
~~~
[root@vm-232-139 upi]# openshift-install create ignition-configs
INFO Consuming Install Config from target directory
INFO Credentials loaded from the "default" profile in file "/root/.aws/credentials"
INFO Ignition-Configs created in: . and auth
INFO Next steps:
INFO To monitor bootstrap process:
./openshift-install --dir <installation_directory> wait-for bootstrap-complete --log-level=info
INFO To monitor installation process:
./openshift-install --dir <installation_directory> wait-for install-complete --log-level=info
[root@vm-232-139 upi]#
~~~
The command should display clearly formatted, copy-paste-ready instructions.
Instructions should be specific to the current installation directory context.
Messages should follow the same INFO logging format for consistency.
3. Why does the customer need this? (List the business requirements here)
- Prevents end users from feeling "lost" after the ignition configs are generated.
- Provides a smoother, guided installation experience — especially important for first-time installers and occasional operators.
- Reduces time spent searching for documentation.
- Promotes consistent operational procedures.
4. List any affected packages or components.
- openshift-install CLI (multi-platform)