Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1193007
Description of problem:
we know that alias interfaces can be configured statically, you can't configure when dhcp is set on same subnet. And currently when you configure a alias interface on same subnet where provisioning is configured and obviously for which bootmode is set to 'DHCP', UI doesn't raise any error/warning on UI.

And user can't set static because provisioning is configured on same subnet. So only way is to add new subnet and use that to configure aliases statically.

I'm not how this can be handled in current design. But I think its a valid case.

Version-Release number of selected component (if applicable):
Satellite-6.1.0-RHEL-6-20150210.0
Sat6.1.0 beta snap2

How reproducible:
always

Steps to Reproduce:
1. create a alias interface on same subnet where provisioning is configured and BootMode set to 'DHCP'
2.
3.

Actual results:
Add_interface form doesn'r raise any warning or error. User gets to know only when alias interface will not be configured on provisioned host.

Expected results:
UI should give some way or raise a warning when submiting the add_interface form for alias interface with bootmode set to dhcp on same subnet.

Additional info: