Comment 7 for bug 475864

I did further testing today. If you go the route of preseeding partman you can get a little closer to the behavior that was working in Jaunty. I have dropped this into a preseed.cfg file

# Selecting proper disk
d-i partman-auto/disk string /dev/vda
# Removing LVM partitions
d-i partman-lvm/device_remove_lvm boolean true
# Picking LVM
d-i partman-auto/method string lvm
# Creating layout
d-i partman-auto/expert_recipe string boot-root :: 512 1024 768 ext4 $primary{ } $bootable{ } method{ format } format{ } use_filesystem{ } filesystem{ ext4 } mountpoint{ /boot } . 15360 18432 20480 ext4 $lvmok{ } method{ format } format{ } use_filesystem{ } filesystem{ ext4 } mountpoint{ / } . 5120 5632 6144 ext4 $lvmok{ } method{ format } format{ } use_filesystem{ } filesystem{ ext4 } mountpoint{ /var } . 1024 512 4096 linux-swap $lvmok{ } method{ swap } format{ } . 1024 2048 3072 ext4 $lvmok{ } method{ format } format{ } use_filesystem{ } filesystem{ ext4 } mountpoint{ /tmp } . 300 400 -1 ext4 $lvmok{ } method{ format } format{ } use_filesystem{ } filesystem{ ext4 } mountpoint{ /disk/trump } .
# Confirm LVM selection
d-i partman-lvm/confirm boolean true
# Finish up
d-i partman/confirm_write_new_label boolean true
d-i partman/choose_partition select finish
d-i partman/confirm boolean true

If I reference this preseed.cfg on the kernel boot line with preseed/url=http://$myurl things work as intended. If I move this to my kickstart file and change the 'd-i' to preseed then everything is honored except the 'partman-auto/expert_recipe string' line, this is being ignored. Instead partman chooses the pre-defined scheme atomic and continues on its marry way. If I replace my expert recipe with 'partman-auto/choose_recipe select multi' this is honored and it uses this scheme properly.

While declaring the preseed.cfg at boot is a work around it breaks our deployment strategy and removes a piece of automation we have in place. Please look at this before release.