+ Reply to Thread
Results 1 to 2 of 2

Thread: forced to issue a boothost -m node after addhost

  1. #1
    dryrye is offline Junior Member
    Join Date
    July 11th, 2009
    Posts
    3
    Downloads
    0
    Uploads
    0

    Default forced to issue a boothost -m node after addhost

    1. When adding an imaged node using addhost I have to issue 'boothost -m nodename' because the /tftpboot/kusu/pxelinux.cfg/MAC-ADDRESS never gets update to boot from localdisk rather than the network once the node is installed. If "boothost -m nodename" is not issued, the node keeps on reinstalling itself.

    2. When adding a node using addhost, at which point should addhost be terminated (Quit the program/F12) once a new node has been detected by addhost? Tried (1) quitting before installation is complete, (2) after installation is complete but new node didn't reboot, and (3) after new node rebooted... each time I still have to issue boothost -m nodename to tell the new node to boot from localdisk.

  2. #2
    mshanker is offline Junior Member
    Join Date
    February 22nd, 2010
    Posts
    1
    Downloads
    0
    Uploads
    0

    Default

    I am having the exact same problem where a node will just keep reinstalling forever. The node state never leaves Expired. Anyone able to figure this one out?

+ Reply to Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts