Bug 1462804

Summary: Adding zFCP LUN in GUI: TypeError: Argument 0 does not allow None as a value
Product: [Fedora] Fedora Reporter: Jan Stodola <jstodola>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 26CC: anaconda-maint-list, dan, g.kaviyarasu, hannsj_uhl, jonathan, mkolman, vanmeeuwen+fedora, vponcova
Target Milestone: ---   
Target Release: ---   
Hardware: s390x   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-29 12:58:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 467765, 1397886    

Description Jan Stodola 2017-06-19 14:58:05 UTC
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[0], args[1], args[2])
  File "/usr/lib64/python3.6/threading.py", line 864, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/lib64/python3.6/site-packages/pyanaconda/threads.py", line 251, in run
    threading.Thread.run(self)
TypeError: Argument 0 does not allow None as a value

Version-Release number of selected component (if applicable):
anaconda-26.21.9-1.fc26.s390x.rpm
python3-blivet-2.1.9-1.fc26.noarch.rpm

How reproducible:
always

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
WWPN: 500507630500c73d
LUN: 4020400700000000
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

Actual results:
anaconda traceback

Expected results:
zFPC LUN successfully attached

Comment 2 Fedora End Of Life 2018-05-03 08:42:58 UTC
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'
of '26'.

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.

Comment 3 Fedora End Of Life 2018-05-29 12:58:12 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.