Bug 1720725

A customer needs to provide custom options. Currently the workaround is:

def build_host(options)
      host = ::Infoblox::Fixedaddress.new(:connection => @connection)
      host.name = options[:hostname]
      host.ipv4addr = options[:ip]
      host.mac = options[:mac]
      host.nextserver = options[:nextServer]
      host.use_nextserver = true
      host.bootfile = options[:filename]
      host.use_bootfile = true
      host.network_view = network_view
      host.options = [{"name"=> "PXE_menu_prompt","num"=> 10,"value"=> "-","vendor_class"=> "EmpirumPXE"},{"name"=> "PXE_discovery_control","num"=> 6,"value"=> "-","vendor_class"=> "EmpirumPXE"},{"name"=> "PXE_boot_menu","num"=> 9,"value"=> "-","vendor_class"=> "EmpirumPXE"},{"name"=> "PXE_boot_servers","num"=> 8,"value"=> "-","vendor_class"=> "EmpirumPXE"}]
      host
end

Additionally, it looks like their Infoblox instance processes the DHCP change for about 1-2 minute and they would like to be able to delay launch of the VM in Satellite.

ANALYSIS:

Adding new fields to the UI/CLI/API is a bigger change which will unlikely to happen in a reasonable timeframe, but if these DHCP options do not change very often, I think I should be able to squeeze in a small feature - configurable option via infoblox.yml file. These options could be set via configuration file during deployment. Limitation is obvious, cannot be different for a single host or a host group.

For the 1-2 minutes delay I filed a PR - new global setting to do explicit delay. Note in this case browser and/or hammer timeout will need to be increased as well: https://github.com/theforeman/foreman/pull/6846

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/27060 has been resolved.

The delay is being implemented in a different BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1724228

Please disregard my last comment, the referenced BZ is installer change.

Backlog only, no errata.

Waiit_after_restart already implemented upstream, but the DHCP options not merged yet.

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/27060 has been resolved.

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/28328 has been resolved.

Tested on Satellite 6.8 Snap 17, tfm-rubygem-smart_proxy_dhcp_infoblox-0.0.16-3.el7sat.noarch.
The feature functionality is as described in the comment #4. Custom dhcp options can be added to /etc/foreman-proxy/settings.d/dhcp_infoblox.yml in the following format:

 :options:
  -
    name: "DHCP option name"
    num: 1234
    value: "A value"
    vendor_class: "A vendor class"


During the host creation, custom DHCP options are sent along to the Infoblox and added to the host record. If vendor_class is used, the option is correctly assigned to the pre-existing Options Space on Infoblox.

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 (Important: Satellite 6.8 release), 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-2020:4366