Description of problem:
We kickstart from a dedicated DHCP network with auto ip assignment. In the kickstart we do not configure this interface anymore for security reasons (to not allow circumventing the firewall).
That means that after kickstart finishes and the system boots this interface has no configuration.
Puppet then uploads the facts with all the interfaces configurations including this Provisioning interface that has only a MAC address but no further IP configuration.
Sat6 parses this Puppet interface facts, but is has no idea that what the Provisioning interface is. And then decides to put it on a random (primary?) interface. Which ofcourse will conflict with correct Subnet used for TFTP booting.
- Create VM HostA with 2 interfaces
NIC1: Main Interface
NIC2: Kickstart interface
- Only configure in the OS NIC1, leave NIC2 unconfigured
- Remove HostA from Sat6 to make sure it will be re-created
- Run puppet agent on HostA, the uplaoded facts will create HostA in Sat6
NIC1 will have both Primary and Provision Flags
The NIC2 will have Provision Flag and assigned the Subnet for TFTP Boot
Ive selected Puppet as component, maybe its not the best fit.
: Sat6 : : Host :
: : :eth1 eth0:
| | |
Provisioning Net Production Net
* You boot the host using eth1 for network boot and run a hostgroup based provisioning (without former configuration of the host in Satellite)
* The kickstart template does not configure eth1
* eth0 is used for production traffic
* During the process you register the host with "subscription-manager" and the first puppet run.
Ideally eth0 should be marked as "primary" and "remote execution", eth1 as "provision".
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.