Project

General

Profile

Actions
Copy link

Bug #1221

closed

Bug with server.next-server in DHCP

Added by Ashley Penney over 12 years ago. Updated almost 12 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Hey Ohad,

Ever since I upgraded to the latest git head I've been having an issue with the proxy putting in the wrong next-server entry:

supersede server.filename = "pxelinux.0";
        supersede server.next-server = 0a:2d:03:65;
        supersede host-name = "cosmos2";

broken ones get:

supersede server.filename = "pxelinux.0";
        supersede server.next-server = 0a:2d:03:42;
        supersede host-name = "brokenhost";

Looking at this closer I know what the issue is but not why - when my puppetserver booted it dhcped to the wrong address (.66, aka :42) and then I manually re-iped it to .101 (aka :65). I have restarted the proxy but it's like it has cached somewhere that the puppet server is on .66 still and is not adapting to the real ip of 101.

Actions
Copy link

Also available in: Atom PDF