This message was deleted.
# harvester
a
This message was deleted.
a
we will check @future-accountant-19088 which dhcp server are you using? and could you paste the related dhcp server config ?
f
sure, im using isc-dhcp-server and here is my config.
Copy code
option domain-name "pxe-dhcp.domain";
option domain-name-servers 10.70.0.2;

default-lease-time 600;
max-lease-time 720;
ddns-update-style none;

option architecture-type code 93 = unsigned integer 16;
authoritative;
host node1 { hardware ethernet 00:0c:29:37:ee:db; }
option tftp-server-name "10.70.0.2";

if exists user-class and option user-class = "iPXE" {
    # iPXE Boot
    if option architecture-type = 00:07 {
      option bootfile-name "<http://10.70.0.2/harvester/ipxe-create>";
    } else {
      option bootfile-name "<http://10.70.0.2/harvester/ipxe-create-efi>";
    }
} else {
    # PXE Boot
    if option architecture-type = 00:07 {
      # UEFI
      option bootfile-name "ipxe.efi";
    } else {
      # Non-UEFI
      option bootfile-name "undionly.kpxe";
    }
}

subnet 10.70.0.0 netmask 255.255.255.0 {
    allow unknown-clients;
        option domain-name-servers 10.70.0.2;
    option routers 10.70.0.1;
    range 10.70.0.4 10.70.0.9;
    next-server 10.70.0.2;
}
Admittedly I haven't worked on this for a few weeks, but I recall getting this template off the harvester docs for pxe boot install, and I had to add the line "option routers 10.70.0.1;" for my dhcp to provide a default route to the harvester installer OS. Even if it's a bogus route without it harvester installer would hang on the run.sh portion and never finish. I just wanted to bring this up because it seems to be a somewhat common issue and even a little note in the docs might help people find the problem before going through a chain of github issue threads 😁
👍 2
🤝 1
a
@future-accountant-19088 Thanks very much. I logged https://github.com/harvester/harvester/issues/4737 to enhance it, feel free to add comments there.