Red Hat Bugzilla – Bug 1271657
Misleading error on empty repodata: "AttributeError: 'NoneType' object has no attribute 'mountpoints'"
Last modified: 2016-03-26 14:14:53 EDT
Description of problem:
I have run into the following error:
anaconda 23.19.6-1 exception report^M
Traceback (most recent call first):^M
File "/usr/lib64/python3.4/site-packages/pyanaconda/packaging/dnfpayload.py", line 550, in spaceRequired^M
for (key, val) in self.storage.mountpoints.items():^M
File "/usr/lib64/python3.4/site-packages/pyanaconda/ui/lib/space.py", line 76, in check^M
needed = self.payload.spaceRequired^M
File "/usr/lib64/python3.4/site-packages/pyanaconda/ui/tui/hubs/summary.py", line 79, in prompt^M
if self._checker and not self._checker.check():^M
File "/usr/lib64/python3.4/site-packages/pyanaconda/ui/tui/simpleline/base.py", line 346, in _mainloop^M
prompt = last_screen.prompt(self._screens[-1])^M
AttributeError: 'NoneType' object has no attribute 'mountpoints'^M
The `mountpoints' suggests there may be something wrong with storage
configuration. Only after a while trying to understand whether there is
something wrong with my kickstart I have found the mirror is corrupted (empty
There is dnf mentioned in the backtrace but the message is IMO not very helpful.
After switching to correct mirror I was able to proceed with installation.
For completeness, this ks installation using following to configure storage:
# Partition clearing information
clearpart --all --initlabel --drives=vda
# Clear the Master Boot Record
# System bootloader configuration
bootloader --location=mbr --boot-drive=vda --append="console=tty0 console=ttyS1,115200 sysrq_always_enabled"
# Precisely define partitions:
part /boot --size=512 --fstype=ext4 --ondisk=vda
part swap --size=256 --ondisk=vda
logvol / --vgname=vg_stacker_D8F4 --name=root --useexisting --fstype=ext4 --size=6144 --mkfsoptions="-O '^64bit'"
The disk layout has one LV, PV (vdb) is directly on disk, no partitions used:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 252:0 0 1G 0 disk
vdb 252:16 0 8G 0 disk
`-vg_stacker_D8F4-root 253:2 0 6G 0 lvm
loop0 7:0 0 343M 1 loop
loop1 7:1 0 2G 1 loop
|-live-rw 253:0 0 2G 0 dm /
`-live-base 253:1 0 2G 1 dm
loop2 7:2 0 512M 0 loop
`-live-rw 253:0 0 2G 0 dm /
zram0 251:0 0 993.5M 0 disk [SWAP]
Version-Release number of selected component (if applicable):
Fedora 23_TC9 compose, Server
Please attach the logs from /tmp as individual, text/plain attachments.
Created attachment 1086756 [details]
Created attachment 1086757 [details]
Created attachment 1086758 [details]
Tarball with logs
This happens only with non interactive KS install.
Using GUI installer proper warning was issued and it is possible to recover by using different location for repos.
I can reliably reproduce this on one particular system with fully automated kickstart install.
*** Bug 1289259 has been marked as a duplicate of this bug. ***
*** Bug 1294700 has been marked as a duplicate of this bug. ***
*** Bug 1304480 has been marked as a duplicate of this bug. ***
I also did general patch for this problem yesterday.
*** Bug 1314095 has been marked as a duplicate of this bug. ***
anaconda-24.13.1-1.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-d85d9ad927
anaconda-24.13.1-1.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-d85d9ad927
anaconda-24.13.1-1.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.