Bug 1573155 - [RFE] change of provisioning interface by utilizing information provided by Puppet facts
Summary: [RFE] change of provisioning interface by utilizing information provided by P...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Puppet
Version: 6.3.0
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Peter Ondrejka
URL:
Whiteboard:
Depends On:
Blocks: 1122832
TreeView+ depends on / blocked
 
Reported: 2018-04-30 11:15 UTC by Nikola Kresic
Modified: 2019-11-04 14:01 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-04 14:01:48 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Nikola Kresic 2018-04-30 11:15:56 UTC
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.



Reproduce:
- 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



Current result:
NIC1 will have both Primary and Provision Flags



Expected result:
The NIC2 will have Provision Flag and assigned the Subnet for TFTP Boot


Additional info:
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".

Comment 3 Bryan Kearney 2019-11-04 14:01:48 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.