Default Installer: No kernel modules were found

This is a problem in the simplestreams data, the archive is moving quicker than the data (kernel and initrd) keeps up. It will be fine once trusty is released.

This is not really acceptable....it means that we cannot pre-test/pre-certify servers prior to GA.

Having our server partners be able to stand up with us at GA time is a goal or ours :-)

This bug also makes it difficult to test or write documentation for the d-i installer, which makes it more likely that there will be additional bugs or documentation slip-ups in the final release.

It may be too late to do anything about it for this release cycle, but some procedure needs to be put in place to prevent this from happening in future releases. Would marking certain kernels for inclusion in the archives in parallel with newer versions, at least until GA, do the trick?

I'm not sure what procedure is in place for updating the simplestreams index right now and I also don't know how feasible/hard it is to keep up to date with the archive. I've asked Scott Moser for some help to see what can be done here.

I'm working on getting daily builds updated.
Once we have them building and publishing with automation, they'll keep up.

Seeing the same message using:
sudo virt-install --connect qemu:///system --name fergus --ram 512 --disk path=/dev/vg1/vm-fergus-root --virt-type kvm --os-variant=ubuntutrusty --location /mnt/ubuntu-iso-14.04-beta2 --graphics none --serial=pty --extra-args="text console=ttyS0 auto"

(loopmounted ubuntu-14.04-beta2-server-i386.iso)

However, if I say Yes, install finishes without issue. Not using preseed but I suspect that with preseed, it would still ask the question (and would still carry on without trouble if I said Yes.)

Peter, I've found that opting to install works sometimes but not other times. Even selecting "Yes" isn't always an option, though -- for instance, if console access is not available.

This was fixed as of Friday with the running kernel being updated to 3.13.0-23-generic. Now that we're on 3.13.0-24-generic, this is an issue yet again.

Experiencing this bug as of today (04/17/2014), fastpath install seems to work. Reran sudo -n -E maas-import-pxe-files and it did not resolve. I expect with the new release today, it's a timing issue perhaps?

I also experimented this "bug" with the final version of 14.04 LTS but with a weird scenario :

1. You change the boot order in the BIOS to use USB Stick first, Hard Disk second, CDROM third or even disable boot from the CD
2. You forgot that you left a Ubuntu 12.02 LTS or 13.10 install CD or whatever old version of Ubuntu in the CDROM drive
3. You prepare a USB stick with the final version of Ubuntu 14.04 LTS and you insert it in a free USB port
4. During the boot (and following the Boot Order) the boot loader of Ubuntu 14.04 LTS will load (choose language etc.)
5. The correct Linux Kernel shipped with Ubuntu 14.04 LTS media will load the correct Ubuntu Installation aka 14.04
6. When Ubuntu will try to access the media it will not load the files from USB stick but from the CDROM...
     so Ubuntu 14.04 will load the files from 12.02 or 13.10 or whatever version presents on the CDROM
7. You will get the message "No kernel modules were found. This probably is due to a mismatch between..."
8. At the end you can fix it by "eject"-ing the old installation CD or use the same kind of installation media during the installation (obvious but not evident to figure out what was happening in my case)

I assume you might also experiment this kind of bug if you have an old Ubuntu CD in while booting the server with MAAS (PXE)

If you want I can create a new bug report with this weird installation "bug" scenario.

I meant to comment on the status earlier, apologies for my delay. The bug has resolved itself on my end, as I expected. There seems to be a lag between the final release and updated pxe files that causes it. I'm not positive. I think if it does resurface it will be short lived and only during new releases (when you're deploying a new release).

I'll be waiting longer in the future before testing maas with newest releases. Hope this helps someone else who observes this. Note this is different than what Guy outlined above.

14.04.2 and this bug is back again.

please note that i'm getting this bug when running a netinstall through cobbler, using the files that come with the 14.04.2 iso

Initrd : /distro/ubuntu-14.04.2-x86_64/install/netboot/ubuntu-installer/amd64/initrd.gz
Kernel : /distro/ubuntu-14.04.2-x86_64/install/netboot/ubuntu-installer/amd64/linux

Broken: (datestamp 30-Jan-2015)
http://archive.ubuntu.com/ubuntu/dists/trusty-updates/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64/

Working: (datestamp 2014-04-15)
http://archive.ubuntu.com/ubuntu/dists/trusty/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64/

Unfortunately, the page on http://cdimage.ubuntu.com/netboot/14.04/ points to trusty-updates, which is the older version (why!?) and is broken.....

Same problem here.
I can't install ubuntu via netboot (newest netboot from ubuntu 14.04.2 server image).
i run every time into the "No kernel Modules were found" error which required interaction to proceed...

@roelof_van_der_kleij
even with the Working image from your post i cant install the image.

Is this still the "out of sync" problem?
when will it get solved?

how can i chosse an alternate wokring image to bypass this error?

sources is preseed currenty:
d-i mirror/country string manual
d-i mirror/http/hostname string ftp.de.debian.org
d-i mirror/http/directory string /debian
d-i mirror/codename string jessie
d-i mirror/suite string jessie
d-i mirror/udeb/suite string jessie
d-i mirror/http/proxy string
d-i mirror/noarch error

the problem occurs again..
is there a working solution for that?

@skaiser, you can try "d-i anna/no_kernel_modules boolean true" if you use a preseed file.