Bug 859540

Seems like NM's get_vendor and get_product methods are returning None in this specific HW case?

Are you able to attach some logs (messages seen on tty1, /tmp/syslog, /tmp/anaconda.log)?

We should at least present something more meaningful than "None" in such cases.

I reran with http://ppc.koji.fedoraproject.org/stage/f18-20121003-Beta-TC1.0/ppc64/iso/Fedora-18-Beta-ppc64-DVD.iso and the problem still occurs.

Remember, this is a ppc machine, so tty1 does not exist.

Created attachment 621189 [details]
syslog

Created attachment 621190 [details]
anaconda.log

[anaconda root@sharpie /]# cat << __EOF__ | python -
#!/usr/bin/python
from gi.repository import NMClient

if __name__ == "__main__":
        client = NMClient.Client.new()

        for con in client.get_active_connections():
                print con
                device = con.get_devices()[0]
                print device
                print device.get_vendor()
                print device.get_product()
__EOF__
<ActiveConnection object at 0x1002fad5960 (NMActiveConnection at 0x1002fb9f140)>
<DeviceEthernet object at 0x1002fad5a00 (NMDeviceEthernet at 0x1002fba6150)>
None
None
<ActiveConnection object at 0x1002fad59b0 (NMActiveConnection at 0x1002fb9f070)>
<DeviceEthernet object at 0x1002fad5a50 (NMDeviceEthernet at 0x1002fba6000)>
None
None

I pushed a patch that replaces None None with empty string, so from anaconda side this BZ should be fixed. If you want to pass it to NM or kernel for fix getting the actual info feel free to do so by changing the component.

Can I get 'udevadm info --attribute-walk --path=/sys/class/net/eth0' on either a running system or the install image?

Also 'udevadm info --query=property  --path=/sys/class/net/eth0'

[root@nibbler ~]# udevadm info --attribute-walk --path=/sys/class/net/eth0

Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

  looking at device '/devices/vio/30000003/net/eth0':
    KERNEL=="eth0"
    SUBSYSTEM=="net"
    DRIVER==""
    ATTR{mtu}=="1500"
    ATTR{type}=="1"
    ATTR{netdev_group}=="0"
    ATTR{flags}=="0x1003"
    ATTR{speed}=="1000"
    ATTR{dormant}=="0"
    ATTR{addr_assign_type}=="0"
    ATTR{dev_id}=="0x0"
    ATTR{duplex}=="full"
    ATTR{iflink}=="2"
    ATTR{addr_len}=="6"
    ATTR{address}=="2a:0f:41:b7:3f:03"
    ATTR{operstate}=="unknown"
    ATTR{broadcast}=="ff:ff:ff:ff:ff:ff"
    ATTR{tx_queue_len}=="1000"
    ATTR{ifalias}==""
    ATTR{ifindex}=="2"
    ATTR{link_mode}=="0"
    ATTR{carrier}=="1"

  looking at parent device '/devices/vio/30000003':
    KERNELS=="30000003"
    SUBSYSTEMS=="vio"
    DRIVERS=="ibmveth"
    ATTRS{name}=="l-lan"

  looking at parent device '/devices/vio':
    KERNELS=="vio"
    SUBSYSTEMS=="vio"
    DRIVERS==""
    ATTRS{name}=="vio"
    ATTRS{devspec}=="<no-node>"
[root@nibbler ~]# udevadm info --query=property  --path=/sys/class/net/eth0
DEVPATH=/devices/vio/30000003/net/eth0
ID_MM_CANDIDATE=1
IFINDEX=2
INTERFACE=eth0
INTERFACE_NAME=eth0
SUBSYSTEM=net
SYSTEMD_ALIAS=/sys/subsystem/net/devices/eth0
TAGS=:systemd:
USEC_INITIALIZED=824509

Two problems here:

1) Anaconda printing "None" because libnm-glib returned NULL for the description; returning NULL is legal here because we can't get any description

2) There is no identifying information for the interfaces in udev; that's because there are no udev rules that add the ID_MODEL_ENC, ID_VENDOR_ENC, ID_MODEL_FROM_DATABASE, or ID_VENDOR_FROM_DATABASE udev database keys.  If we add some udev rules that pull that information from somewhere and stuff it into those keys, then NM will pick them up.

To verify things are working correctly:

$ udevadm info --query=property --path=/sys/class/net/eth0
DEVPATH=/devices/pci0000:00/0000:00:19.0/net/eth0
ID_BUS=pci
ID_MM_CANDIDATE=1
ID_MODEL_FROM_DATABASE=82567LM Gigabit Network Connection
ID_MODEL_ID=/sys/devices/pci0000:00/0000:00:19.0
ID_VENDOR_FROM_DATABASE=Intel Corporation
ID_VENDOR_ID=0x8086
IFINDEX=3
INTERFACE=eth0
INTERFACE_NAME=eth0
SUBSYSTEM=net
SYSTEMD_ALIAS=/sys/subsystem/net/devices/eth0
TAGS=:systemd:
USEC_INITIALIZED=5755360

If you see the ID_MODEL_FROM_DATABASE or ID_MODEL_ENC keys in this dump, then we expect NetworkManager to provide them via libnm-glib, which is what Anaconda uses to show them in the UI.  We would expect them to show in the UI as well.

anaconda-18.17-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/anaconda-18.17-1.fc18

Package anaconda-18.17-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-18.17-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-16295/anaconda-18.17-1.fc18
then log in and leave karma (feedback).

anaconda-18.18-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/anaconda-18.18-1.fc18

Package anaconda-18.18-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-18.18-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-16402/anaconda-18.18-1.fc18
then log in and leave karma (feedback).

anaconda-18.19-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/anaconda-18.19-1.fc18

This bug looks to have been fixed for many anaconda builds now but missed being closed. If you find you are still experiencing it with Fedora 18 Beta (RC1) or later, please re-open the bug.