Bug 1478141 - Anaconda gives a traceback if there is InfiniBand hardware present during an attempt to install
Anaconda gives a traceback if there is InfiniBand hardware present during an ...
Status: NEW
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
26
All Unspecified
unspecified Severity high
: ---
: ---
Assigned To: Anaconda Maintenance Team
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-08-03 13:05 EDT by Doug Ledford
Modified: 2017-08-03 13:05 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Anaconda traceback debug file (367.74 KB, text/plain)
2017-08-03 13:05 EDT, Doug Ledford
no flags Details

  None (edit)
Description Doug Ledford 2017-08-03 13:05:57 EDT
Created attachment 1308804 [details]
Anaconda traceback debug file

Description of problem:

If the machine in question has InfiniBand hardware installed, anaconda will load the ib_ipoib module, this will create an ib0 device (and possibly more ib devices depending on the number of interfaces present).  Anaconda will then give a traceback and fail to install due to a SettingsNotFoundError('ib0',) in the pyanaconda.nm code.

Version-Release number of selected component (if applicable):

Latest Fedora 26 RC as well as current rawhide

How reproducible:

100%

Steps to Reproduce:
1. Attempt to install on machine with InfiniBand hardware
2. ?
3. Boom

Actual results:

Boom.

Expected results:

Install.

Additional info:

Traceback:

Starting installer, one moment...
anaconda 27.19-1 for Fedora Rawhide (pre-release) started.
 * installation log files are stored in /tmp during the installation
 * shell is available on TTY2
 * if the graphical installation interface fails to start, try again with the
   inst.text bootoption to start text installation
 * when reporting a bug add logs from /tmp as separate text/plain attachments
16:56:15 Running pre-installation scripts
16:56:15 Running pre-installation scripts
+ command -v curl
                 + curl --help
                              + grep -q '.*--retry'
                                                   16:56:16 Not asking for VNC because of an automated install
16:56:16 Not asking for VNC because of an automated install
16:56:16 Not asking for VNC because text mode was explicitly asked for in kickstart
16:56:16 Not asking for VNC because text mode was explicitly asked for in kickstart

An unknown error has occured, look at the /tmp/anaconda-tb* file(s) for more details

=============================================================================== 
Traceback (most recent call first):
  File "/usr/lib64/python3.6/site-packages/pyanaconda/nm.py", line 799, in nm_device_setting_value
    raise SettingsNotFoundError(name)
  File "/usr/lib64/python3.6/site-packages/pyanaconda/ui/tui/spokes/network.py", line 84, in _load_new_devices
    if nm.nm_device_setting_value(name, "connection", "slave-type"):
  File "/usr/lib64/python3.6/site-packages/pyanaconda/ui/tui/spokes/network.py", line 63, in initialize
    self._load_new_devices()
  File "/usr/lib64/python3.6/site-packages/pyanaconda/ui/tui/hubs/__init__.py", line 70, in setup
    spoke.initialize()
  File "/usr/lib64/python3.6/site-packages/pyanaconda/ui/tui/hubs/summary.py", line 49, in setup
    should_schedule = TUIHub.setup(self, environment=environment)
  File "/usr/lib64/python3.6/site-packages/pyanaconda/ui/tui/__init__.py", line 182, in setup
    should_schedule = obj.setup(self.ENVIRONMENT)
  File "/sbin/anaconda", line 729, in <module>
    anaconda._intf.setup(ksdata)
pyanaconda.nm.SettingsNotFoundError: SettingsNotFoundError('ib0',)

What do you want to do now?
1) Report Bug
2) Debug
3) Run shell
4) Quit

Please make your choice from above:

Note You need to log in before you can comment on or make changes to this bug.