I ran the tests again[1] with an updated packaging branch[2] which adds the syslinux-dev package as dependency but got another failure, this time a missing /usr/lib/syslinux/chain.c32 file.
Looks like the path for that file changed on utopic's syslinux-common:
So I think there are two bugs here, one is the missing dependency, so import_boot_images can find the pxelinux.0 file. Another one is the hardcoded /usr/lib/syslinux path in provisioningserver/boot/pxe.py which ends up pointing to the wrong place on utopic.
I ran the tests again[1] with an updated packaging branch[2] which adds the syslinux-dev package as dependency but got another failure, this time a missing /usr/lib/ syslinux/ chain.c32 file.
Looks like the path for that file changed on utopic's syslinux-common:
ubuntu@utopic:~$ dpkg -L syslinux- common| grep chain syslinux/ modules/ bios/chain. c32 syslinux/ modules/ efi64/chain. c32 syslinux/ modules/ efi32/chain. c32 doc/syslinux- common/ txt/chain. txt.gz
/usr/lib/
/usr/lib/
/usr/lib/
/usr/share/
So I think there are two bugs here, one is the missing dependency, so import_boot_images can find the pxelinux.0 file. Another one is the hardcoded /usr/lib/syslinux path in provisioningser ver/boot/ pxe.py which ends up pointing to the wrong place on utopic.
[1] http:// d-jenkins. ubuntu- ci:8080/ view/MAAS/ job/utopic- adt-maas- manual/ 30/artifact/ results/ artifacts/ maas-logs/ var/log/ maas/celery. log
[2] lp:~matsubara/maas/syslinux-dev-dep-utopic