Bug 1798874 - unable to add a fcoe disk as there is no nic listed
Summary: unable to add a fcoe disk as there is no nic listed
Keywords:
Status: CLOSED DUPLICATE of bug 1798876
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-06 08:11 UTC by lnie
Modified: 2020-02-06 12:14 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-02-06 11:09:30 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description lnie 2020-02-06 08:11:31 UTC 
Description of problem:
1 click Add a disk in the Installation Destination page
2 click "Add FCOE SAN"
3 click "ADD Fcoe disk"

This happens because  nm_client.get_devices() return value for device['device-type'] is GLib.Variant('i', 1) rather than 1 now,
As a result,though anaconda detected nic but failed to put it in the nicCombo

Version-Release number of selected component (if applicable):
Fedora-Server-dvd-x86_64-Rawhide-20200204.n.0.iso

How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Radek Vykydal 2020-02-06 11:09:30 UTC 
As this bug belongs to the part of installer (FCoE configuration in GUI) which is not used on running (F31) system, just when installing from installation images, and we are not planning to do F31 installation images / isos respin, I am going to close this bug as a duplicate of bug 1798876 filed for the same issue for rawhide. If you think it makes sense to fix the issue also for F31 anaconda feel free to reopen the bug.

*** This bug has been marked as a duplicate of bug 1798876 ***
Comment 2 lnie 2020-02-06 12:14:02 UTC 
Thanks for closing this,I have created this bug by mistake,actually, f31 is not affected.
Note You need to log in before you can comment on or make changes to this bug.