Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1765676 - initial-setup crashes in Rawhide: "AttributeError: '<CompositeObject>' object has no attribute 'SplitKickstart'"
Summary: initial-setup crashes in Rawhide: "AttributeError: '<CompositeObject>' object...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: initial-setup
Version: rawhide
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Martin Kolman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: openqa
Depends On:
Blocks: F32BetaBlocker
TreeView+ depends on / blocked
 
Reported: 2019-10-25 17:25 UTC by Adam Williamson
Modified: 2019-10-31 19:27 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-31 19:27:07 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Adam Williamson 2019-10-25 17:25:04 UTC 
openQA KDE 'no user' install test (where we install without creating a user, expecting initial-setup to run on first boot) is failing in Rawhide ATM, because initial-setup fails to run. It's crashing:

Oct 24 03:00:38 ibm-p8-kvm-03-guest-02.virt.pnr.lab.eng.rdu2.redhat.com initial-setup[1042]: 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.8/site-packages/initial_setup/__init__.py", line 381, in run
     self._load_kickstart()
   File "/usr/lib/python3.8/site-packages/initial_setup/__init__.py", line 225, in _load_kickstart
     boss.SplitKickstart(kickstart_path)
 AttributeError: '<CompositeObject>' object has no attribute 'SplitKickstart'

This violates Basic criterion "A system installed with a release-blocking desktop must boot to a log in screen where it is possible to log in to a working desktop using a user account created during installation or a 'first boot' utility." when installing KDE without creating a user.
Comment 1 Martin Kolman 2019-10-25 18:09:39 UTC 
We hit that issue yesterday and it should be fixed in initial-setup-0.3.77-1.
Comment 2 Adam Williamson 2019-10-25 18:21:33 UTC 
Cool, thanks.
Comment 3 Adam Williamson 2019-10-31 19:27:07 UTC 
The test passed in most recent Rawhide, so this looks good now.
Note You need to log in before you can comment on or make changes to this bug.