Bug 2021072

Description of problem:
using inst.ks=nfs:auto ip=ens3:dhcp to boot RHEL8.4 installation, the filename option set in the dhcp server configuration is ignored by NetworkManager and not propagated to dracut/anaconda.
Kickstart is instead searched in /kickstart on the dhcpd server.
This breaks a behavior that has been present in all previous RHEL releases.

The documentation in:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/performing_an_advanced_rhel_installation/kickstart-and-advanced-boot-options_installing-rhel-as-an-experienced-user

states:
In the previous example, next-server is the DHCP next-server option or the IP address of the DHCP server itself, and filename is the DHCP filename option, or /kickstart/.

But setting inst.ks does not make the use of the filename dhcp option to work.
The behavior of the software doesn't match the documentation.

Further observations:
anaconda/dracut/fetch-kickstart-net.sh is looking for /tmp/net.$netif.lease if inst.ks=nfs:auto is specified.
But in /tmp, there is only dhclient.ens3.dhcpopts and net.ens3.dhcpopts

To sum up:
The behavior of the installer does not match the documentation
inst.ks=nfs:auto is not present in the official documentation, but the code is meant to work that way
NetworkManager ignores the filename dhcp option and the option is not propagated to dracut/anaconda
anconda/dracut/fetch-kickstart-net.sh is looking for possibly the wrong file


Version-Release number of selected component (if applicable):
NetworkManager-1.30.0-10.el8
anaconda-33.16.4.15-1.el8

How reproducible:
Systematic

Steps to Reproduce:
1.Set up a dhcp server to serve kickstarts using the filename option
example:
 host ehvsrv700sv { hardware ethernet 52:54:00:FD:D1:8E; fixed-address 10.101.9.181; filename "/data/built/test/kickstart/"; }

2.boot RHEL8 with inst.ks=nfs:auto ip=ensX:dhcp or inst.ks ip=ensX:dhcp (following documentation)
3.

Actual results:
Installation looks for kickstart at /kickstart instead of using the filename dhcp option.

Expected results:
RHEL8 installation fetches kickstart at the location present in the filename dhcp option.

Additional info: