Bug 1193007

Summary: when configuring an alias interface user should get some warning if bootmode is set to 'DHCP' under provisioning subnet
Product: Red Hat Satellite Reporter: Sachin Ghai <sghai>
Component: WebUIAssignee: Marek Hulan <mhulan>
WebUI sub component: Foreman QA Contact: Sachin Ghai <sghai>
Status: CLOSED CURRENTRELEASE Docs Contact:
Severity: high    
Priority: medium CC: bkearney, sthirugn
Version: 6.1.0Keywords: Triaged
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/9434
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-12 13:55:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1193987    
Attachments:
Description Flags
configuring a alias interface on dhcp subnet raises validation error. none

Description Sachin Ghai 2015-02-16 11:30:29 UTC 
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:
Comment 2 Bryan Kearney 2015-02-18 21:03:19 UTC 
Created redmine issue http://projects.theforeman.org/issues/9434 from this bug
Comment 3 Bryan Kearney 2015-03-22 18:04:59 UTC 
Moving to POST since upstream bug http://projects.theforeman.org/issues/9434 has been closed
-------------
Marek Hulán
Applied in changeset commit:a45253c2b7c747b15506dddc4efa86396c6ef53f.
Comment 7 Sachin Ghai 2015-05-08 13:23:34 UTC 
Verified with sat6.1 GA snap3 compose2.

This issue is still reproducible. I defined a alias interface with dhcp selected subnet and while provisioning the discovered host. Host provisioning started with any warning or error.
Comment 8 Sachin Ghai 2015-05-11 12:31:11 UTC 
Verified with sat6.1 GA snap3.

UI raises error when user tries to configure an alias interface on DHCP subnet (or when bootmode is set to DHCP). 

UI raises error: subnet boot mode is not Static
Comment 9 Sachin Ghai 2015-05-11 12:32:33 UTC 
Created attachment 1024217 [details]
configuring a alias interface on dhcp subnet raises validation error.
Comment 10 Sachin Ghai 2015-05-11 12:35:28 UTC 
Verified with sat6.1 GA snap3.

As per comment8 and 9 moving this to verified.
Comment 11 Bryan Kearney 2015-08-11 13:28:40 UTC 
This bug is slated to be released with Satellite 6.1.
Comment 12 Bryan Kearney 2015-08-12 13:55:14 UTC 
This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.