After deploying a Linux image to a new host, the PXE process attempts to reboot, but does not fall through to the GRUB of the newly deployed image. Instead, it continuously recycles, ending with two attempts failing with the following message:

…no configuration methods succeeded (http://ipxe.org/xxxxxxx…)

If I physically switch off the machine and then restart - it loads a FOG menu briefly and then automatically loads the new OS correctly, as expected.

Any suggestions on how to overcome having to physically switch the terminal off and on again?

Thanks
Jose

@george1421 Fantastic! Many thanks.

@Tom-Elliott many thanks.

I am now able to authenticate and access the APIs. The original docs were not clear about the fact that one needs to submit BOTH 'fog-api-token AND ‘fog-user-token’ headers.

Will experiment and try to figure out the required content of the body messages for the POST/PUT operations that I need to work with and will reach out to you if I get stuck with a particular call.

Hi,

I have followed the curl example in the docs for all three types of authentication (Basic, fog-api-token and fog-user-token) against the basic info endpoint, but I am either getting a 401 (Unauthorized) or 403 (Forbidden).

Is there full API documentation online? Amongst other things, I would like to add/update host entries via the API, but require detailed spec…

Thanks,
Jose

@george1421 - Thanks.

Is there a way to initially just start an interactive shell, so that I can test all the individual commands that will eventually make up the unattended script?

Hi,

I would like to pass a text file with host specific settings (like hostname, etc.) to a Linux host, so that on first startup after imaging, the host can perform some specific customization tasks.

I am guessing that ‘postdownloadscripts’ are the appropriate mechanism…? How do I target a specific file with specific settings to a specific host?

A simple end-to-end working example would be greatly appreciated!

Thanks,
Jose