Hi, I’m using VMware Vsphere 6.7 and I have a script which is using a RHEL kickstart file from my HTTP server. So when building my new VM, everything work just find if I’m RHEL 7.x iso. It’s booting normally, getting the kickstart from my HTTP server… But when doing the same thing from the RHEL 8.x ISO, it’s not able to ger the kickstart from my HTTP server. It’s like the network is not available. I have tried to creat my VM manually, breaking the boot process and entering the boot sequence by hand, specifying the HTTp kickstart file and it’s working just kine. So I thing PACKER is doing something different with a RHEL 8.x making the network not available/reachable!!!
how does your boot_command looks like? mine is working like this with Rhel8.2:
"boot_command": [
"<up><wait><tab><wait> text ks=http://{{ .HTTPIP }}:{{ .HTTPPort }}/ks-manual.cfg<enter><wait5>"
],
"http_directory": "kickstart",
"http_port_min": "8000",
"http_port_max": "8000",Hi Deanso,
Thanks for your help. It’s now booting correctly and performing the installation… but at he end, I’m getting:
Installation completed. Press ENTER to continue
How can I bypass this? I need the installation to continue by itself… because I have other scripts that is waiting to run to continue my server setup!!!
Thanks again for the help!!!
Ghislain Lévesque
DLGL
T: (450) 979-4646
When you have “convert_to_template”: true, option set, it will end in a template:
==> vsphere-iso: Convert VM into template…
==> vsphere-iso: Clear boot order…
Build ‘vsphere-iso’ finished.
In your kickstart file, you can set extra scripts which you need to run on the running machine, like so:
%post --log=/root/ks-post.log
curl http://hostname:8000/after_install.sh | sudo bash
%end
hostname is in this case the name of the packer http server,the same where you are running your packer build command.
1 Like
Thank you for your help. Everything is now working.
Have a great day
Ghislain Lévesque
DLGL
T: (450) 979-4646