Answering for the script part since I don't know kickstart.
I wonder how you know that it's not running; whether that be "the results didn't happen" or some log file complaint that the script wasn't run for some reason. Remember that mount may require root or better yet, sudo privileges. To do sudo in a script you may have to set it up so that the user id running the script can perform sudo without needing the password. Or at least verify that root is the ID running the script.
To debug I'd recommend you place output into a log file.
Add an echo line at the top of the script, output stdout and stderr to that same log file. See if you can get the user ID and runlevel when this script is running. This way you can determine (A) if the script is running at all, and (B) if steps in the script are not working because of circumstances you didn't foresee.
# Obviously replace <username> in all this with a user ID directory which you know the script can access.
echo "Post kickstart script running." >> /home/<username>/post-ks.log;
echo "Script run by user: $USER/`/usr/bin/whoami`. At runlevel: $RUNLEVEL/`/usr/bin/who -r`" >> /home/<username>/post-ks.log;
# I use both $USER and whoami because the $USER variable may not be populated.
# I also use both $RUNLEVEL and who -r for the same reason, and many times $RUNLEVEL is NOT populated.
# No guarantees that you'll learn much except that the script did or didn't run, but if it's being run by user <blah-blah> and
# that user is nothing you've ever heard of, and also does not have the privileges to just execute mount without sudo privileges,
# then that would be a problem. I'd also consider finding the path and using exacting paths for all shell commands.
/bin/mkdir -p /mnt/temp &>> /home/<username>/post-ks.log;
# PROBABLY THE ERROR IS THE LACK OF THE -p ARGUMENT IN YOUR mkdir COMMAND.
# Get stdout and stderr into your log and find out if there was a problem creating this directory, also use the -p argument
# because it will not complain if the parent wasn't there and also will not complain if /mnt/temp already exists.
/bin/mount -o nolock 192.168.50.32:/puclic/centos /mnt/temp &>> /home/<username>/post-ks.log;
# Should that say public? I think a simple typo which may or may not be in the script by the way, get stdout and stderr
/bin/openvt -s -w -- /mnt/temp/postscript.sh &>> /home/<username>/post-ks.log;
/bin/umount /mnt/temp &>> /home/<username>/post-ks.log;
# NOTE that you umount here but you don't remove the directory; hence when you try to create that directory with mkdir, it will
# cause an error because the second time and beyond, that directory exists, and the script will likely exit at that point.
# After ANY shell command, the variable $? contains the result. Zero means it worked, any other value means it probably didn't
# work. So you can have an echo include saying stuff like:
echo "Result of umount was $?" >> /home/<username>/post-ks.log;