Description of problem:
I got the following traceback when running text mode kickstart installation on an s390x system with zFCP disk:
anaconda 23.19.7-1 exception report
Traceback (most recent call first):
File "/usr/lib/python3.4/site-packages/blivet/devicetree.py", line 655, in make_unformatted_dasd_list
File "/usr/lib64/python3.4/site-packages/pyanaconda/ui/tui/spokes/storage.py", line 99, in __init__
to_format = storage.devicetree.make_unformatted_dasd_list(getDisks(self.storage.devicetree))
File "/usr/lib64/python3.4/site-packages/pyanaconda/ui/tui/hubs/__init__.py", line 64, in setup
spoke = spokeClass(self.app, self.data, self.storage, self.payload, self.instclass)
File "/usr/lib64/python3.4/site-packages/pyanaconda/ui/tui/hubs/summary.py", line 50, in setup
should_schedule = TUIHub.setup(self, environment=environment)
File "/usr/lib64/python3.4/site-packages/pyanaconda/ui/tui/__init__.py", line 180, in setup
should_schedule = obj.setup(self.ENVIRONMENT)
File "/usr/sbin/anaconda", line 1320, in <module>
AttributeError: 'ZFCPDiskDevice' object has no attribute 'busid'
Similar traceback also reproduced when running:
* manual installation in text mode
* kickstart installation in both text and vnc mode
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. have an s390x system with zFCP disk
2. run one of these installations:
a) manual installation in text mode
b) kickstart installation in text mode
c) kickstart installation in vnc mode
Not reproducible when running manual installation in vnc mode or when no zFCP disk is present
Proposed as a Freeze Exception for 23-final by Fedora user jstodola using the blocker tracking app because:
Violating the following criterion:
Only proposing as an exception, since this is happening on s390x (secondary architecture)
Discussed at 2015-10-19 freeze exception review meeting: https://meetbot.fedoraproject.org/fedora-blocker-review/2015-10-19/f23-blocker-review.2015-10-19-16.00.html . Accepted as a freeze exception issue as a serious issue in secondary storage.
Note as we're in release week and we have no outstanding anaconda blockers it is unlikely this will make it in if we release this week. If we slip and other anaconda issues are discovered, it's possible this may make it in. We'd like to ask the anaconda team to *only* apply a fix for this if it's very safe (i.e. clearly isolated to the zfcp codepath).
(In reply to email@example.com from comment #3)
> other anaconda issues are discovered, it's possible this may make it in.
> We'd like to ask the anaconda team to *only* apply a fix for this if it's
> very safe (i.e. clearly isolated to the zfcp codepath).
Yes, it is. Actually I'm pretty sure the fix for this will be in blivet, but my statement remains true -- this is only going to affect a function that gets run on s390x.
python-blivet-1.12.8-1.fc23 anaconda-23.19.9-1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-da7ada8825
All cases from comment 0 retested, no longer able to reproduce with python-blivet-1.12.8-1.fc23.
Thanks, moving to VERIFIED.
anaconda-23.19.10-1.fc23, python-blivet-1.12.8-1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
$ su -c 'dnf --enablerepo=updates-testing update anaconda python-blivet'
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-da7ada8825
Closing as fixed (see comment 6)
...except the update has not been pushed stable.
anaconda-23.19.10-1.fc23, python-blivet-1.12.8-1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.