Project

General

Profile

Actions
Copy link

Bug #1381

closed

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

Added by Paul Kelly about 13 years ago. Updated almost 13 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Paul Kelly
Category:
DHCP
Target version:
0.4.1
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

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 2 (0 open — 2 closed)

Related to Foreman - Bug #1420: bootserver ip lookup fails if not managing dnsClosedPaul Kelly12/31/2011Actions
Related to Foreman - Bug #1451: Host creation fails if ":tftp_servername:" is set in proxy-settingsClosedOhad Levy01/18/2012Actions
Actions
Copy link
 #1

Updated by Paul Kelly about 13 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100
Actions
Copy link
 #2

Updated by Ohad Levy about 13 years ago

  • Target version set to 0.4.1
Actions
Copy link
 #3

Updated by Ohad Levy almost 13 years ago

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

Actions
Copy link
 #4

Updated by Ohad Levy almost 13 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

Actions
Copy link

Also available in: Atom PDF