Description of problem:

Discovery Red Hat kexec always uses a url to fetch the provisioning template with the option "static=yes" set, regardless of the subnet configuration.

How reproducible:

Always

Is this issue a regression from an earlier version:

Unsure

Steps to Reproduce:

1. Create a subnet with boot mode set to dhcp

2. discovery a system

3. provision the system using the subnet created on step 1

4. check the provisioned system (or even inside anaconda the ks.cfg file and the inst.ks url that will be using static=yes

Actual behavior:
Always configure host to use static IP configuration, even if the subnet is configured to use dhcp

Expected behavior:
respect the subnet definition and use dhcp or static based on it.

Business Impact / Additional info:

Starting on 6.15 this impacts the final built system. Until 6.15, the provisioning template would create an ifcfg file with the information from the subnet. Starting on 6.15, we don't create that file anymore leveraging only anaconda to configure the network.