RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.

Description of problem:


Initial setup does not load on the first boot after installation of Server with GUI from CDN. This happens only if Account is used as authentication method. It appears that problem is in parsing of anaconda-ks.cfg file. 

Journalctl:
Jan 06 07:08:50 localhost.localdomain initial-setup[1305]: kickstart parsing failed: The following problem occurred on line 18 of the kickstart file:
the following arguments are required: --organization, --activation-key
Jan 06 07:08:50 localhost.localdomain initial-setup[1305]: Initial Setup startup failed due to invalid kickstart file

See attached logs for more details.


Version-Release number of selected component (if applicable):
anaconda 29.19.2.6-1.el8
RHEL-8.2.0-20191219.0 x86_64

How reproducible:
Always

Steps to Reproduce:
1. Start RHEL-8.2 installation
2. Enter "Connect to Red Hat" spoke and register (use Account for authentication)
3. In software selection spoke, choose Server with GUI
4. Finish installation and reboot

Actual results:
Initial-setup is not present on the first boot.

Expected results:
Initial-setup is present on the first boot.

Additional info:
Installation with authentication via Activation Key does work as expected.

Created attachment 1650415 [details]
attach_logs

Created attachment 1650416 [details]
dbus.log

Created attachment 1650417 [details]
dnf.librepo.log

Created attachment 1650418 [details]
hawkey.log

Created attachment 1650419 [details]
ifcfg.log

Created attachment 1650420 [details]
journal_full.log

Created attachment 1650421 [details]
journal.log

Created attachment 1650422 [details]
lvm.log

Created attachment 1650423 [details]
packaging.log

Created attachment 1650424 [details]
program.log

Created attachment 1650425 [details]
storage.log

Created attachment 1650426 [details]
X.log

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, 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-2020:1584