Red Hat Bugzilla – Bug 1462804
Adding zFCP LUN in GUI: TypeError: Argument 0 does not allow None as a value
Last modified: 2018-05-03 04:42:58 EDT
Description of problem:
anaconda 26.21.9-1 exception report
Traceback (most recent call first):
File "/usr/lib64/python3.6/site-packages/gi/overrides/BlockDev.py", line 798, in wrapped
ret = orig_obj(*args, **kwargs)
File "/usr/lib/python3.6/site-packages/blivet/zfcp.py", line 58, in __init__
self.fcplun = blockdev.s390.zfcp_sanitize_lun_input(fcplun)
File "/usr/lib/python3.6/site-packages/blivet/zfcp.py", line 339, in add_fcp
d = ZFCPDevice(devnum, wwpn, fcplun)
File "/usr/lib64/python3.6/site-packages/pyanaconda/ui/gui/spokes/advstorage/zfcp.py", line 185, in _discover
self.zfcp.add_fcp(args, args, args)
File "/usr/lib64/python3.6/threading.py", line 864, in run
File "/usr/lib64/python3.6/site-packages/pyanaconda/threads.py", line 251, in run
TypeError: Argument 0 does not allow None as a value
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. start vnc installation
2. proceed to the Installation Destination spoke
3. try to add a zFCP LUN (I used these values):
Device number: a007
4. Press the "Start Discovery" button - anaconda says that discovery failed - "You have not specified a FCP LUN or the number is invalid"
5. I modified the LUN format: 0x4020400700000000 and retried - anaconda traceback appeared
zFPC LUN successfully attached
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 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'
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 26 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.