Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
I'm using tip deveopment branch and am trying to get TFTP to work, but on booting the node, it doesn't do anything after getting an IP from DHCP.
Though, when the node PXE boots, I get the correct
I then changed the DHCP configuration according to this page:
Which ended up as:
and changed the HTTP config to listen on
I'm not an expert in PXE booting, but I got a few lessons from this:
Am I doing something terribly wrong?
For any fixes in OpenHPC recipes, please open an issue with that project. We're not responsible for what they have put together.
See /etc/warewulf/dhcpd-template.conf (ex. https://github.com/warewulf/warewulf3/blob/development/provision/etc/dhcpd-template.conf), which is populated by running
I suggest starting with a clean system. Rebuilding RPMs if they're older than a week or so. Ignore most instructions from OHPC about Warewulf install and config. Install the Warewulf development branch RPMs, go through configs in /etc/warewulf updating as needed and run
Regarding OpenHPC, don't worry, I was just asking for an opinion, so I can propose the right thing from warewulf's point of view.
I'll do as you propose, wipe and start warewulf directly via
But I still get the same error, even when I only leave the right filename (no if/else block) with the patch relative to the TFTP root:
The rest looks correct:
I'll start fresh and update this ticket.
Bah sorry misspoke, iPXE binaries are under the tftpboot path. iPXE configs and bootstraps are under /var/warewulf as you pointed out.
It's worth doing a sanity check
If all this fails, can you post a tcpdump of the dhcp, tftp, and http traffic during an attempted boot?
Excellent. If you want httpd to work with selinux enforcing you can run:
The new warewulf-provision-server-selinux rpm does this on install via post-script.
Thanks Ben! We probably could add that package in the OpenHPC recipe, or even better, make it as a dependency for warewulf-provision-ohpc package, so that we always run it upon installation.
Adding to the recipe will create the problem of having to update once warewulf is updated (and docs become wrong), so the latter is definitely a better alternative, if we can avoid any conflict (run before creating the directories, if that matters).
Alternatively I can move the above into the postscripts of the parent warewulf-provision-server RPM, but this will add
I agree you shouldn't push our own (OpenHPC's) choices into everyone else's installations.
But it would also be good to have a warning / installation message to make sure users are aware of the issues, or they'll be lost if they're not used to SELinux.