Bug 2000650
| Summary: | Anaconda doesn't inform when the rhsm kickstart command fails | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Jan Stodola <jstodola> | |
| Component: | anaconda | Assignee: | Martin Kolman <mkolman> | |
| Status: | CLOSED ERRATA | QA Contact: | Release Test Team <release-test-team-automation> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 8.5 | CC: | jkonecny, pzatko, rvykydal | |
| Target Milestone: | rc | Keywords: | Triaged | |
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | anaconda-33.16.7.5-1.el8 | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 2000652 (view as bug list) | Environment: | ||
| Last Closed: | 2022-11-08 09:17:10 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1956679 | |||
RHEL-9 clone: bug 2000652 Marking as Verified: Tested as the fix passes acceptance criteria Follow-up bug reported as BZ2096199 Checked that anaconda-33.16.7.5-1.el8 is in nightly compose RHEL-8.7.0-20220619.0 Moving to VERIFIED 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 (anaconda bug fix and enhancement update), 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/RHBA-2022:7462 |
Description of problem: When running a kickstart installation and the installation source is set to Red Hat CDN using the rhsm kickstart command, anaconda doesn't inform the user when the registration fails (for example when an invalid activation key is provided): ... Starting automated install.... Saving storage configuration... Checking storage configuration... ================================================================================ ================================================================================ Installation 1) [x] Language settings 2) [x] Time settings (English (United States)) (America/New_York timezone) 3) [!] Installation source 4) [!] Software selection (Error setting up software (Error checking software source) selection) 5) [x] Installation Destination 6) [x] Kdump (Automatic partitioning (Kdump is enabled) selected) 7) [x] Network configuration 8) [ ] User creation (Wired (enp1s0) connected) (No user will be created) Please make a selection from the above ['b' to begin installation, 'q' to quit, 'r' to refresh]: In case there is a dvd.iso attached to the system, anaconda automatically uses it for the installation instead. Version-Release number of selected component (if applicable): RHEL-8.4 GA anaconda-33.16.4.15-1.el8 How reproducible: Always Steps to Reproduce: 1. run a kickstart installation containing the following line: rhsm --organization=unknown_organization --activation-key=unknown_key Actual results: No error message describing why the installation fails. Or, if there is a usable DVD/USB media in the system, anaconda automatically switches to that media. Expected results: The installation is interrupted if the rhsm kickstart command fails. The user can see an error message.