@Tom-Elliott Thanks for the clarification, but please let me know if I can at least somehow avoid resizing the current partitions (especially boot partition), such as by checking Multiple Partition Image - Single Disk (Not Resizable) - (2)?

Hello, it looks something is wrong with you backend.
Are you able to open from the browser:

http://192.168.1.22/fog/service/ipxe/boot.php
http://192.168.1.22/fog/service/ipxe/bzImage

?

@Sebastian-Roth after 4 years I have the same issue. My golden image partitions look like this:

sda                         8:0    0    12G  0 disk 
├─sda1                      8:1    0   572M  0 part /boot/efi
├─sda2                      8:2    0   1.8G  0 part /boot
└─sda3                      8:3    0   9.7G  0 part 
  └─ubuntu--vg-ubuntu--lv 252:0    0   9.7G  0 lvm  /

After deployment the boot partition has been enlarged to the size of the entire disk instead of LVM:

nvme0n1                   259:0    0 465.8G  0 disk 
├─nvme0n1p1               259:1    0   572M  0 part /boot/efi
├─nvme0n1p2               259:2    0 455.5G  0 part /boot
└─nvme0n1p3               259:3    0   9.7G  0 part 
  └─ubuntu--vg-ubuntu--lv 252:0    0   9.7G  0 lvm  /

What should I do in this case?
A. Prepare new golden image without LVM (I want to avoid it)?
B. Change image type from Single Disk - Resizable - (1) to Multiple Partition Image - Single Disk (Not Resizable) - (2) ?

There is no big deal for me to extend LVM partition after deployment manually if FOG is unable to do this. I just don’t want it to resize other partition than LVM.