Bug 2055295 - options bootfile and next-server created on Infoblox for hosts even if they are empty on Satellite
Summary: options bootfile and next-server created on Infoblox for hosts even if they a...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Infoblox integration
Version: 6.9.8
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Lukas Zapletal
QA Contact: Radovan Drazny
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-16 15:45 UTC by Joniel Pasqualetto
Modified: 2022-07-20 08:45 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-07-20 08:45:38 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Joniel Pasqualetto 2022-02-16 15:45:06 UTC
Description of problem:

Create a host on Satellite with PXE-Loader set to None, the options filename and next-server are left empty. Then the fixed-address is created on Infoblox and those options are set, but with empty values.

It seems more logical to not set those options when the values are empty.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Create a host and set pxe-loader to none
2. look at the properties of the host on infoblox.
3.

Actual results:

Options are set with empty values

Expected results:
Options not set at all

Additional info:

The block of code in [1] seems to be reason for this.  host.use_nextserver and  host.use_bootfile are always set to true, independently of the values in options[:filename] and options[:nextServer]

[1]: https://github.com/theforeman/smart_proxy_dhcp_infoblox/blob/80bf4371b4c01d25dbea7cf093badcc9ed858229/lib/smart_proxy_dhcp_infoblox/fixed_address_crud.rb#L57-L60

Comment 2 Leos Stejskal 2022-07-20 08:45:38 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team. Thank you.


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