Bug #13619
closed
Second virtual NIC on host gets configured to use DHCP, even though initial static configuration is provided
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1283954
Description of problem:
Second virtual NIC on host gets configured to use DHCP, even though initial static configuration is provided
Version-Release number of selected component (if applicable):
Satellite 6.1.3
Any Compute Resource either VMware or RHEV
How reproducible:
100%
Steps to Reproduce:
1. Create a host for provisioning and add the second interface in the Network tab while creating the host with static IP address
2. Create 2 NICs in the Virtual Machine tab for the Compute Resource
3. Provision the system which successfully gets provisioned, but the second network information provided previous gets discarded and a default values are assigned to it where BOOTPROTO is set to DHCP.
Actual results:
Second NIC static information is discarded and set as a DHCP
Expected results:
Should set the IP information as provided in the webUI
Additional info:
Screenshots attached to the bug for further information
Updated by Dominic Cleal over 8 years ago
- Status changed from New to Need more information
Can you please confirm if this happens on a stable release with Foreman 1.8+'s networking enhancements? There has been a lot of work in this area and kickstart installs should be fine with multiple interfaces.
Updated by Marek Hulán over 7 years ago
- Category set to Network
- Status changed from Need more information to Rejected
It works for me with recent Foreman, BOOTPROTO is set to none if the subnet boot mode is static. I think Dominic is right. I'm closing this, if you have a reproducer with Foreman 1.8+ please reopen with reproducing steps. Thank you.