Project

General

Profile

Bug #1381

Foreman uses fqdn internally for DHCP nextServer. This should be the IP address.

Added by Paul Kelly over 7 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
DHCP
Target version:
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

Conflict resolution requires that the attrs returned by the smart-proxy match the attrs that foreman uses. Foreman uses a hostname internally whilst the smart-proxy always returns an IP address.

This results in bogus conflicts.


Related issues

Related to Foreman - Bug #1420: bootserver ip lookup fails if not managing dnsClosed2011-12-31
Related to Foreman - Bug #1451: Host creation fails if ":tftp_servername:" is set in proxy-settingsClosed2012-01-18

Associated revisions

Revision 7fe22657 (diff)
Added by Paul Kelly over 7 years ago

fixes #1381 - nextServer should be handled internally as an IP address not a hostname

Signed-off-by: Paul Kelly <>

Revision 66be1d4b (diff)
Added by Paul Kelly over 7 years ago

fixes #1381 - nextServer should be handled internally as an IP address not a hostname

Signed-off-by: Paul Kelly <>

History

#1 Updated by Paul Kelly over 7 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

#2 Updated by Ohad Levy over 7 years ago

  • Target version set to 0.4.1

#3 Updated by Ohad Levy over 7 years ago

this patch breaks if dhcp is enabled, but dns is off :-\

#4 Updated by Ohad Levy over 7 years ago

Ohad Levy wrote:

this patch breaks if dhcp is enabled, but dns is off :-\

and thanks to Paul it is fixed in #1420

Also available in: Atom PDF