Description of problem:
1. started vnc installation on s390x
2. proceeded to the Installation destination spoke
3. selected all DASD disks
4. tried to enter the custom partitioning spoke -> traceback
Version-Release number of selected component:
The following was filed automatically by anaconda:
anaconda 23.19.4-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/gui/spokes/storage.py", line 786, in _check_dasd_formats
dasds = self.storage.devicetree.make_unformatted_dasd_list(self.selected_disks)
File "/usr/lib64/python3.4/site-packages/pyanaconda/ui/gui/spokes/storage.py", line 915, in on_back_clicked
rc = self._check_dasd_formats()
AttributeError: 'str' object has no attribute 'busid'
cmdline: /usr/bin/python3 /sbin/anaconda
cmdline_file: repo=http://s390pkgs.fedoraproject.org/compose/23_Beta_RC1/23/Server/s390x/os/ ro ramdisk_size=40000 cio_ignore=all,!condev rd.dasd=0.0.3527 rd.dasd=0.0.3727 rd.dasd=0.0.3627 rd.znet=qeth,0.0.0a00,0.0.0a01,0.0.0a02,layer2=1,portno=0,portname=FOOBAR ip=10.16.105.198::10.16.111.254:21:rtt7.s390.bos.redhat.com:enccw0.0.0a00:none nameserver=10.16.36.29 nameserver=10.11.5.19 inst.noverifyssl BOOT_IMAGE=0
dnf.rpm.log: Oct 05 08:05:48 INFO --- logging initialized ---
release: Cannot get release name.
Created attachment 1079858 [details]
Created attachment 1079859 [details]
Created attachment 1079860 [details]
Created attachment 1079861 [details]
Created attachment 1079862 [details]
Created attachment 1079864 [details]
Created attachment 1079867 [details]
Also happens when trying to reclaim disk space.
Proposed as a Blocker for 23-final by Fedora user jstodola using the blocker tracking app because:
Violating the following criteria:
Note that this only applies to the s390x architecture.
Pretty sure this won't be approved since it happens on a secondary arch, but final freeze isn't until next week, and I can fix this before then. Should be a low-impact change.
Discussed at 2015-10-05 blocker review meeting: https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2015-10-05/f23-blocker-review.2015-10-05-16.00.html . Rejected as a release blocker as it affects only a secondary arch; accepted as a freeze exception as it seems like a serious issue for that arch and we generally grant freeze exceptions for such cases. Of course, the fix should only be taken if it is safe.
(In reply to firstname.lastname@example.org from comment #16)
> Of course, the fix should only be taken if it is safe.
Yes, it is quite safe -- it is a small fix isolated only to s390x pieces of code, nothing in blivet is touched (saw some mention of concern about that in the meeting logs).
anaconda-23.19.7-1.fc23 python-blivet-1.12.7-1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-c70e34d416
anaconda-23.19.7-1.fc23, python-blivet-1.12.7-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 python-blivet anaconda'
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-c70e34d416
No longer able to reproduce with anaconda-23.19.7-1.fc23.
Thanks, moving to VERIFIED.
anaconda-23.19.7-1.fc23, python-blivet-1.12.7-1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.