+++ This bug was initially created as a clone of Bug #1155026 +++

Description of problem:
When an Anaconda/Initial Setup addon is missing in the environment and the kickstart file contains an %addon section with some header option specified (like: %addon com_example_foo --argument='example'), parsing such kickstart results in an error. That is a bug because a missing addon shouldn't trigger any tracebacks as its %addon kickstart section can be simply ignored.

--- Additional comment from Fedora Blocker Bugs Application on 2014-10-21 11:40:51 CEST ---

Proposed as a Freeze Exception for 21-beta by Fedora user vpodzime using the blocker tracking app because:

 This bug causes the Initial Setup to crash not allowing user creation and other things during the first boot.

--- Additional comment from Martin Kolman on 2014-10-22 13:36:16 CEST ---

I'll just ad that due to this bug Initial Setup will not only not be shown on first start after install but it will also never be disabled. This means it will try to start on every boot just to crash, potentially slowing down the boot a bit and maybe also introducing some interruptions to the Plymouth boot screen.

--- Additional comment from Adam Williamson (Red Hat) on 2014-10-22 19:56:23 CEST ---

Discussed at 2014-10-22 freeze exception review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2014-10-22/f21-blocker-review.2014-10-22-16.03.log.txt . For now we're rejecting this, but we're open to a re-proposal.

It's somewhat unclear from the description whether a typical deployment of any Fedora media are going to hit this, or if it only hits custom use of initial-setup which none of our media do. If you can only hit it by using a custom kickstart that specifies %addon we're inclined to reject it, because we don't think that's a very common thing to do and not worth breaking freeze for at this point.

If you'd like us to re-consider this, please re-propose with more details as to why it's worth breaking freeze to fix this. thanks!

--- Additional comment from Vratislav Podzimek on 2014-10-23 10:54:39 CEST ---

(In reply to Adam Williamson (Red Hat) from comment #3)
> Discussed at 2014-10-22 freeze exception review meeting:
> http://meetbot.fedoraproject.org/fedora-blocker-review/2014-10-22/f21-
> blocker-review.2014-10-22-16.03.log.txt . For now we're rejecting this, but
> we're open to a re-proposal.
> 
> It's somewhat unclear from the description whether a typical deployment of
> any Fedora media are going to hit this, or if it only hits custom use of
> initial-setup which none of our media do. If you can only hit it by using a
> custom kickstart that specifies %addon we're inclined to reject it, because
> we don't think that's a very common thing to do and not worth breaking
> freeze for at this point.
> 
> If you'd like us to re-consider this, please re-propose with more details as
> to why it's worth breaking freeze to fix this. thanks!
Okay guys, let me express it more clearly:
Initial Setup doesn't run on default installation where it is supposed to run due to this bug. The kdump anaconda addon has been added to the installation images (and it's UI can be enabled by inst.kdump_addon=on) which results in an %addon section being written out to every installation's /root/anaconda-ks.cfg file which is then processed by the Initial Setup. Due to this bug IS crashes and leaves itself enabled so it runs and crashes on every boot. If no user account is created in the installation process, no user can be created before users get to KDM/XDM/?DM.

This doesn't affect GNOME because Initial Setup is not installed together with GNOME as that provides its own initial setup utility.

Re-proposing as I really think this is worth fixing as FE.