Description of problem:

How reproducible:

Is this issue a regression from an earlier version:

Interfaces marked as managed but that don't have a subnet assigned to them should include options to not start on boot like -noipv4 -noipv6 and onboot=false

Steps to Reproduce:

1. Create a host with an interface marked as "managed" on Satellite. Don't assign a subnet to it

2. After provisioning, observe NetworkManager logs to see it trying to initialize the interfaces

Actual behavior:
Interfaces are configured as if they were to be configured via dhcp (mod=auto on network manager profile)

Expected behavior:
Interfaces should be disabled.

Business Impact / Additional info: