Comment 4 for bug 1667790

Hi,

This failure was a result of netcfg segfault seen on the logs.

------------------8<--------------->8----------------------------
Feb 24 06:31:51 netcfg[3724]: DEBUG: Writing wireless options for p4p1
 Feb 24 06:31:51 netcfg[3724]: DEBUG: Success!
 Feb 24 06:31:52 main-menu[2545]: WARNING **: Configuring 'netcfg' failed with error code 139
 Feb 24 06:31:52 main-menu[2545]: WARNING **: Menu item 'netcfg' failed.
 Feb 24 06:31:52 kernel: [ 62.915859] netcfg[3724]: segfault at 0 ip 00007f1ab154e34f sp 00007ffc781aec78 error 4 in libc.so.6[7f1ab14b1000+1ba000]
------------------8<--------------->8----------------------------

We have root caused a bug in the qede driver that was triggering this.

qede IOCTL implementation returns '0' instead of -EOPNOTSUPP for all IOCTL requests made by user.
wireless-lib used by netcfg as part of the PXE boot process tries learning whether our interface is wireless via sending an IOCTL; As we return '0', it learns we're a wireless interface and does some incorrect configurations. Later, netcfg would segfault due to broken information.
Fixed qede IOCTL callback to return -EOPNOTSUPP to everything other than the timesync requests.

Having said that, does netcfg also require a fix to gracefully fail in this case with a meaningful error message, rather than segfault so that it's easier to debug such issues.