Description of problem:

Creating a system that will be provisioned through a vlan interface doesn't work properly.

The way the vlan interface is defined on anaconda is wrongly using the device over which the vlan is supposed to be defined.

If the user creates a vlan inteface called ens3.123 over the physical interface ens3, our templates will create something like this:

network --device=ens3.123 --hostname host0.example.com --noipv6 --mtu=1500 --bootproto static --ip=10.1.2.10 --netmask=255.255.255.0 --gateway=10.1.2.254 --vlanid=123 --interfacename=vlan123 --nodns

This is wrong, since the "device" options is supposed to be the actual device over which the vlan is to be set, not the vlan device name. Expected line:

network --device=bond0 --hostname host0.example.com --noipv6 --mtu=1500 --bootproto static --ip=10.1.2.10 --netmask=255.255.255.0 --gateway=10.1.2.254 --vlanid=123 --interfacename=vlan123 --nodns

How reproducible:

Always

Is this issue a regression from an earlier version:

No

Steps to Reproduce:

1. Create a host with a managed vlan interface (don't need to be used for provisioning)

Actual behavior:
device is wrongly defined inside the provisioning template and interface won't be operational when the installation is done

Expected behavior

interface to be working properly after provisioning

Business Impact / Additional info: