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
Bug 1699091 - pyanaconda.modules.common.errors.DBusError 'NoneType' object has no attribute 'upper'
Summary: pyanaconda.modules.common.errors.DBusError 'NoneType' object has no attribute...
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 30
Hardware: aarch64
OS: Linux
Target Milestone: ---
Assignee: Radek Vykydal
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: ARMTracker
TreeView+ depends on / blocked
Reported: 2019-04-11 18:36 UTC by Paul Whalen
Modified: 2020-05-04 08:11 UTC (History)
10 users (show)

Fixed In Version: anaconda-31.10-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-05-04 08:11:43 UTC
Type: Bug

Attachments (Terms of Use)
kickstart (8.57 KB, text/plain)
2019-04-11 18:37 UTC, Paul Whalen
no flags Details
anaconda log (4.77 KB, text/plain)
2019-04-11 18:38 UTC, Paul Whalen
no flags Details
syslog (300.50 KB, text/plain)
2019-04-12 14:02 UTC, Paul Whalen
no flags Details

Description Paul Whalen 2019-04-11 18:36:55 UTC
Description of problem:
Attempting to install a Fedora 30 nightly in Beaker (Fedora-30-20190408.n.0).

Starting installer, one moment...
anaconda 30.25.4-1.fc30 for Fedora 30 (pre-release) started.
 * installation log files are stored in /tmp during the installation
 * shell is available on TTY2
 * if the graphical installation interface fails to start, try again with the  
   inst.text bootoption to start text installation                             
 * when reporting a bug add logs from /tmp as separate text/plain attachments  
13:46:00 Running pre-installation scripts                                      
Traceback (most recent call last):
  File "/sbin/anaconda", line 593, in <module>                                 
  File "/usr/lib64/python3.7/site-packages/pyanaconda/", line 310, in
  File "/usr/lib64/python3.7/site-packages/pyanaconda/", line 289, in
  File "/usr/lib64/python3.7/site-packages/pyanaconda/modules/common/task/", line 60, in sync_run_task
  File "/usr/lib/python3.7/site-packages/pydbus/", line 102, in __call__
    raise error
pyanaconda.modules.common.errors.DBusError: 'NoneType' object has no attribute 'upper'

Version-Release number of selected component (if applicable):
anaconda 30.25.4-1.fc30

Comment 1 Paul Whalen 2019-04-11 18:37:33 UTC
Created attachment 1554619 [details]

Comment 2 Paul Whalen 2019-04-11 18:38:01 UTC
Created attachment 1554621 [details]
anaconda log

Comment 3 Radek Vykydal 2019-04-12 10:14:53 UTC
Please attach also syslog log file.
And/or add a link to the failed beaker job if available.

Comment 4 Paul Whalen 2019-04-12 14:02:20 UTC
Created attachment 1554803 [details]

Comment 5 Radek Vykydal 2019-04-12 15:14:03 UTC
1) The cause of the crash is using:

- ksdevice=bootif boot option with BOOTIF value missing from boot options (usually added by PXE "ipappend 2"):

BOOT_IMAGE=/images/ ks= ksdevice=bootif netboot_method=grub2

- with a device defined in kickstart without --device option, in which case boot option "ksdevice" is used to supply value to --device ("bootif"):

network --bootproto=dhcp

2) PR to prevent the crash:

3) updates image with the patch (against version from the description):

can be checked / applied by using boot option


or kickstart command


Comment 6 Jeff Bastian 2019-05-16 20:48:40 UTC
See bug 1710993 for a request for Beaker to stop adding ksdevice=bootif by default.

Comment 7 Paul Whalen 2019-05-17 00:33:37 UTC
This unfortunately still affects Fedora 30 final installations in beaker, working with ksdevice=bootif removed from the kernel args.

I checked Fedora-Rawhide-20190515.n.1 which includes anaconda 31.12-1.fc31, and it appears to be working as expected even with 'ksdevice=bootif' included.

Comment 9 Ben Cotton 2020-04-30 21:59:27 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

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