What were you trying to do that didn't work?

Installation of a z/VM guest via a qeth network device. The device was usable during the installation, but it was not present on the installed system.

The problem happens when the qeth network device is configured via DHCP. In case of a static IPv4 configuration on the installation kernel command line, this problem doesn't happen and the network device is created and configured correctly on the installed system.

Provided archive contains logs from both DHCP and static IPv4 installations with the following files:

• anaconda logs from the installation
• nmcli_con_show_enc600 - connection details printed during the installation
• enc600.nmconnection - NM config file from the installed system

Please provide the package NVR for which bug is seen:

RHEL-10.0-20240605.93
NetworkManager-1.47.90-2.el10
anaconda-40.22.3.3-1.el10
dracut-101-1.el10

How reproducible:

Always on a z/VM guest

Steps to reproduce

1. Run an installation on a z/VM guest with a qeth network device, use DHCP to configure the network device.
2. Reboot to the installed system.

Expected results

qeth network device up and running.

Actual results

qeth device doesn't exist on the installed system:

 [root@localhost ~]# ip a                                                        
ip a                                                                            
1:  [36mlo:  [0m<LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN gro
up default qlen 1000                                                            
    link/loopback  [33m00:00:00:00:00:00 [0m brd  [33m00:00:00:00:00:00 [0m     
    inet  [35m127.0.0.1 [0m/8 scope host lo                                     
       valid_lft forever preferred_lft forever                                  
    inet6  [34m::1 [0m/128 scope host noprefixroute                             
       valid_lft forever preferred_lft forever                                  
[root@localhost ~]#