Description of problem:
The kickstart file used for provisioning machines always contains

network --bootproto=dhcp --hostname=...

command, which conflicts with the static networking setup used with s390x machines. I believe this became an issue after anaconda changed their network setup code to rely on NetworkManager.

The "network" command shouldn't be used when the machine has network pre-configured from dracut/initrd environment, like our s390x guests.


Version-Release number of selected component (if applicable):
26.5 as used at beaker.engineering.redhat.com

How reproducible:
100%

Steps to Reproduce:
1. run a reservesys job
2. select s390x
3. select Fedora30
4. supply ip= kernel option used by RHEL-8

Actual results:
- traceback from /tmp/anamon with
    socket.gaierror: [Errno -2] Name or service not known
- network connectivity lost in the "middle" of the provisioning process (right after the pre-install script finished)

Expected results:
- no traceback, machine accessible over network

Additional info:
"network --bootproto=dhcp" breaks installations with static networking setup outside beaker too
The anamon crash isn't fatal, but the loss of network connectivity is.