Version-Release number of selected component: anaconda-26.2-1 Additional info: reporter: libreport-2.8.0 addons: com_redhat_docker, com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-S-dvd-x86_64-rawh quiet executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.8.0-0.rc6.git0.1.fc26.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: rawhide Truncated backtrace: Traceback (most recent call last): File "/usr/lib64/python3.5/site-packages/pyanaconda/threads.py", line 251, in run threading.Thread.run(self, *args, **kwargs) File "/usr/lib64/python3.5/threading.py", line 862, in run self._target(*self._args, **self._kwargs) File "/usr/lib64/python3.5/site-packages/pyanaconda/ui/gui/spokes/advstorage/iscsi.py", line 221, in _discover r_password=credentials.rPassword) File "/usr/lib/python3.5/site-packages/blivet/iscsi.py", line 372, in discover args = GLib.Variant("(sqa{sv}", ipaddr, port, auth_info) TypeError: __new__() takes 3 positional arguments but 5 were given
Created attachment 1200595 [details] File: anaconda-tb
Created attachment 1200596 [details] File: anaconda.log
Created attachment 1200597 [details] File: backtrace
Created attachment 1200598 [details] File: description
Created attachment 1200599 [details] File: dnf.librepo.log
Created attachment 1200600 [details] File: environ
Created attachment 1200601 [details] File: hawkey.log
Created attachment 1200602 [details] File: ifcfg.log
Created attachment 1200603 [details] File: lsblk_output
Created attachment 1200604 [details] File: nmcli_dev_list
Created attachment 1200605 [details] File: packaging.log
Created attachment 1200606 [details] File: program.log
Created attachment 1200607 [details] File: storage.log
Created attachment 1200608 [details] File: syslog
New lorax seems to have fixed https://bugzilla.redhat.com/show_bug.cgi?id=1347415 , but iSCSI installs now hit this error a bit later. See e.g. https://openqa.fedoraproject.org/tests/34236 . Assuming this will hit F25 as well once lorax goes stable there, nominating as a Final blocker: "The installer must be able to detect (if possible) and install to supported network-attached storage devices."
https://github.com/rhinstaller/blivet/pull/510
Discussed at 2016-09-19 blocker review meeting: [1]. We decided to tentatively accept it as a final blocker: If the affected software hits stable repos, this will violate "The installer must be able to detect (if possible) and install to supported network-attached storage devices." for iSCSI and therefore be a blocker. Punting for the moment. [1] https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2016-09-19/
(In reply to Vratislav Podzimek from comment #16) > https://github.com/rhinstaller/blivet/pull/510 Merged.
python-blivet-2.1.4-1.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2016-d8691b1b14
python-blivet-2.1.4-1.fc25 has been pushed to the Fedora 25 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-d8691b1b14
Discussed during the 2016-09-26 blocker review meeting: [1] The decision to classify this bug as an AcceptedBlocker was made as the affected Lorax build is currently pending stable, and we expect that it will affect F25. We find that this bug violates the Final criteria: "The installer must be able to detect (if possible) and install to supported network-attached storage devices." [1] https://meetbot.fedoraproject.org/fedora-blocker-review/2016-09-26/f25-blocker-review.2016-09-26-16.04.txt
(In reply to Fedora Update System from comment #20) > python-blivet-2.1.4-1.fc25 has been pushed to the Fedora 25 testing The update has been unpushed, but python-blivet-2.1.6-1.fc25 has been pushed stable two weeks ago. Adam, can you please retest this? Thanks.
Well, it's a little hard to be sure, as iSCSI is still broken due to https://bugzilla.redhat.com/show_bug.cgi?id=1378156 , and I can't tell for sure if this one happen(s/ed) *before* that or *after* it. But since it's claimed fixed, let's go ahead and close it; we can re-open if it shows up again after #1378156 is fixed.