Posts made by JRyanCon

@george1421 Thanks, that is helpful to know.

@george1421 Is the fog.postdownload only run if you push a FOG image to the target? I am not using images at the moment. The client is pointing to an unpacked iso and letting the user manually walk through the install, or using a kickstart to automate the install.

Note that, I know that i could use the %POST section of the kickstart, but we plan to also use Linux images, as well as Windows images, attended and unattended installs. I wanted to try this for.postdownload capability thinking it might give me a common process no matter the type of install done.

:OS.RHEL.75
:RHEL75NetInstall
set base <IP_ADRESS>/iso/PXE/RHEL/75
kernel ${base}/images/pxeboot/vmlinuz initrd=initrd.img repo=${base}
initrd ${base}/images/pxeboot/initrd.img
boot

@george1421 Yes, I included the call to the script in the fog.postdownload script. I also tried putting the echo into the fog.downloadscript directly. I also do not see any echo to the screen after the install completes. It doesnt seem like the fog.downloadscript is called/running.

[root@raspschpxe1001 postdownloadscripts]# cat /images/postdownloadscripts/fog.postdownload
#!/bin/bash
## This file serves as a starting point to call your custom postimaging scripts.
## <SCRIPTNAME> should be changed to the script you're planning to use.
## Syntax of post download scripts are
#. ${postdownpath}<SCRIPTNAME>

#. ${postdownpath}fog.postTest

. /usr/share/fog/lib/funcs.sh

echo "TESTING START"

debugPause

@george1421 I do not see any print statements to the screen.

I thought I would try the debug mode, so I added it to the FOG iPXE menu and booted to it. When I do, I get prompted to enter a UN/PW. I tried the FOG admin UN/PW, and seems like it didnt take it. It asks again for the UN/PW then just seems to boot to one of the iPXE options, with no difference in the behavior.

I tried looking around for how to create a debug mode account, but only found this page, which looks far out of date.
https://wiki.fogproject.org/wiki/index.php/Debug_Mode_is_asking_me_for_a_password

@george1421 I read the link you provided and have a few questions:

1. It looks like there are some functions being called like getHardDisk and debugPause. Are these functions from . /usr/share/fog/lib/funcs.sh?

2. Where can i see all the functions available in funcs.sh?

3. When I do a echo called from a file called from fog.postdownload, it does not print to the screen. How do I see the output?

I am running FOG 1.5.2. From what I have read, if I want to run post install tasks, I can created a script, and call that script from /images/postdownloadscripts/fog.postdownload. I have tried adding a very simple script that just creates a file to test it, but the file is not created. I also tried just adding the “touch” command directly to the fog.postdownload file, and that also didn’t seem to do anything.

Is there anything that I need to do to enable the fog.postdownload file to be called, or it always is called by default? Anyway to debug this?

I do not see anywhere in the FOG GUI to edit the fog.postdownload file or ensure that it is enabled?

[root@raspschpxe1001 ~]# cat /images/postdownloadscripts/fog.postdownload
#!/bin/bash
## This file serves as a starting point to call your custom postimaging scripts.
## <SCRIPTNAME> should be changed to the script you're planning to use.
## Syntax of post download scripts are
#. ${postdownpath}<SCRIPTNAME>

. ${postdownpath}fog.postTest

[root@raspschpxe1001 ~]# cat /images/postdownloadscripts/fog.postTest
#!/bin/bash

. /usr/share/fog/lib/funcs.sh

touch ~/testfile