Bug 1891621 - initial-setup crashes with "KeyError: 'logging'"
Summary: initial-setup crashes with "KeyError: 'logging'"
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: initial-setup
Version: rawhide
Hardware: All
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Martin Kolman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: openqa
Depends On:
Blocks: F34FinalBlocker
TreeView+ depends on / blocked
 
Reported: 2020-10-26 20:54 UTC by Adam Williamson
Modified: 2020-10-29 16:00 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-29 16:00:38 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Adam Williamson 2020-10-26 20:54:28 UTC
In current Rawhide, after doing an install of KDE live with no user created or root password set during install, initial-setup should run on the first boot after install, but it crashes with a traceback:

Oct 26 12:28:59 localhost.localdomain initial-setup[735]: Initial Setup crashed due to unhandled exception:
  Traceback (most recent call last):
    File "/usr/libexec/initial-setup/initial-setup-graphical", line 10, in <module>
      is_instance.run()
    File "/usr/lib/python3.9/site-packages/initial_setup/__init__.py", line 381, in run
      self._load_kickstart()
    File "/usr/lib/python3.9/site-packages/initial_setup/__init__.py", line 202, in _load_kickstart
      commandMap = dict((k, kickstart.commandMap[k]) for k in SUPPORTED_KICKSTART_COMMANDS)
    File "/usr/lib/python3.9/site-packages/initial_setup/__init__.py", line 202, in <genexpr>
      commandMap = dict((k, kickstart.commandMap[k]) for k in SUPPORTED_KICKSTART_COMMANDS)
  KeyError: 'logging'

this violates at least Final criterion "If an initial setup utility is run or intended to be run after the first boot of the installed system, then it must start successfully and each page or panel of the initial setup utility should withstand a basic functionality test" - https://fedoraproject.org/wiki/Fedora_33_Final_Release_Criteria#First_boot_experience - so proposing as an F34 Final blocker.

Comment 1 Adam Williamson 2020-10-26 21:34:20 UTC
Looks like this is due to this anaconda commit:
https://github.com/rhinstaller/anaconda/commit/8a9f5e9667d3cd40a5328d6db2b1acf47e829646

so I guess 'logging' should just get dropped from SUPPORTED_KICKSTART_COMMANDS?

Comment 2 Martin Kolman 2020-10-26 22:08:06 UTC
(In reply to Adam Williamson from comment #1)
> Looks like this is due to this anaconda commit:
> https://github.com/rhinstaller/anaconda/commit/
> 8a9f5e9667d3cd40a5328d6db2b1acf47e829646
> 
> so I guess 'logging' should just get dropped from
> SUPPORTED_KICKSTART_COMMANDS?

Yeah. I think that should work - we recently dropped support for setting log level via that command (as we found out it did not really do anything for quite a while) and it looks like this is the unexpected fallout of that in Initial Setup.

I'll write a fix shortly. :)


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