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:
Doug, could I have some beaker machine loaned to debug? I used to use rdma-dev-10.lab.bos.redhat.com for development some time ago.
(In reply to Radek Vykydal from comment #1) > Doug, could I have some beaker machine loaned to debug? > I used to use rdma-dev-10.lab.bos.redhat.com for development some time ago. I was able to borrow it today.
The crash occurs in text mode in case there is any Infiniband device that has not been activated by boot options or kickstart.
https://github.com/rhinstaller/anaconda/pull/1221
Proposed as a Freeze Exception for 27-final by Fedora user rvykydal using the blocker tracking app because: The bug prevents text (also automated text) installations on machines with infiniband device in cases where there is any infiniband device that has not been activated by boot options or kickstart. The issue is there since F26, it would be nice to have it fixed.
Discussed during the 2017-10-23 blocker review meeting: [1] The decision to classify this bug as an AcceptedFreezeException was made as it can't be fixed by an update and will inconvenience anyone who runs into it. [1] https://meetbot.fedoraproject.org/fedora-blocker-review/2017-10-23/f27-blocker-review.2017-10-23-16.00.txt
anaconda-27.20.4-2.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-501b8f778f
anaconda-27.20.4-2.fc27 has been pushed to the Fedora 27 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-2017-501b8f778f
anaconda-27.20.4-3.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-501b8f778f
anaconda-27.20.4-3.fc27 has been pushed to the Fedora 27 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-2017-501b8f778f
anaconda-27.20.4-4.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-501b8f778f
anaconda-27.20.4-4.fc27 has been pushed to the Fedora 27 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-2017-501b8f778f
anaconda-27.20.4-4.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.