Red Hat Bugzilla – Bug 1166163
[RFE] Add ancestry NICs and allow interfaces with same MAC
Last modified: 2017-02-23 15:47:26 EST
Virtual interfaces can have same MAC addresses so we should validate uniqueness only for physical interfaces. I'll add ancestry to NICs table, parents will be physical interfaces.
Created from redmine issue http://projects.theforeman.org/issues/6444
I am pulling down important features from the 1.7 release. You can read more abotu this feature at http://theforeman.org/manuals/1.7/index.html#Releasenotesfor1.7 I believe that QE will be done by the community on this feature.
Moving to POST since upstream bug http://projects.theforeman.org/issues/6444 has been closed ------------- Marek Hulán https://github.com/theforeman/foreman/pull/1565 ------------- Marek Hulán Applied in changeset commit:d455f32cde8fa60e41474bbaab0b8af1d7aded50.
hi please provide verification steps thanks
As part of this change, these was added: Support for virtual and physical interfaces NIC facts parsing change and we create interfaces in Foreman according to facts we receive. Added support for virtual and physical interfaces. IPMI facts parsing and BMC NIC creation based on custom facts that are present in discovery image. NIC orchestration is now optional and can be set for every interface. All created interfaces based on facts (BMC or Managed) are not managed. Allow subnet selection without domain for NIC so we can use DHCP only. Suggest IP addresses even without proxy by Foreman itself. Foreman finds first free IP on a particular Subnet based on records in database. I think Sachin already tested most of these, maybe you could ask him.
Verified with sat6.1 GA snap5. - now user can define virtual interfaces like alias/bond/vlan etc. On provisioning a host, user will see all defined interfaces configured on provisioned host. - while discovery, bmc interface can automatically be discovered and user can see under discovered_host --> network --> interfaces - User can defined unmanaged/managed BMC interfaces, but BMC feature should be enabled on proxy. - subnet has two new options. IPAM and bootmode. User can explicitly create dhcp subnet or static subnets. - Similarly IPAM mode can be used for auto IP address assignment. Satellite finds free IP in a selected subnet and auto suggest while creating new host. - User can see ENC output of all the configured interfaces I'll attach all these in the form of screen shots just to cover what all has been tested. Note: there are few limitations with alias/bond/vlan is that you should know the mac address of interface. For example: alias MAC is the same that is the MAC of interface it's attached to, so you have to know this MAC.
Created attachment 1029923 [details] subnet page has two new options IPAM and BootMode. User can define dhcp/static subnets.
Created attachment 1029924 [details] while discovering a host, BMC interface artifacts auto discovered and can be seen under edit/new host --> network --> interface
Created attachment 1029925 [details] alias/bond/vlan and BMC interfaces are configured
Created attachment 1029930 [details] enc output of configured interfaces
Created attachment 1030350 [details] configured BMC interface
Moving this verified as comments 9 to 14.
This bug is slated to be released with Satellite 6.1.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2015:1592