Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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:
Moving to POST since upstream bug http://projects.theforeman.org/issues/9434 has been closed
-------------
Marek Hulán
Applied in changeset commit:a45253c2b7c747b15506dddc4efa86396c6ef53f.
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.
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