failed for unknown reasons

Wow, I've absolutely no idea what's causing this. Nasty. The logs should be sufficient though ...

I belive I get the error if I do:

anna-install libcrypto0.9.8-udeb

I'm attaching everything you could possibly want, just cuz I have it handy.

I am guessing you should be able to reproduce it easy enough using whatever alt-installer method you normally use, (like using qemu + alt-cd.iso) - If not, I can supply a simple script.

ps - amusing: The reason I am installing openssh-client-udeb is so I can scp the log files when there is an error. So the error is caused by preparing for an error; I got the error because I was expecting one. I think I have found a new class of
http://en.wikipedia.org/wiki/Heisenbug :)

This will break at least the use of network-console for 8.04.1, as well as Carl's use case of installing openssh-client-udeb for debugging purposes on a netboot install, unless fixed.

The problem is essentially that, because libdebian-installer doesn't have proper support for multiple Packages files, it gets confused by the same package being in all of hardy, hardy-security, and hardy-updates (we point it to all of those quite intentionally, so that we can update at least the netboot installer effectively). anna ends up trying to install the same package multiple times and getting tied up in knots. This has actually been a long-term deficiency in libdebian-installer, and I think fixing it is (a) hard and (b) requires an ABI break; however, it seems like we could work around it in anna fairly straightforwardly.

This has to go in net-retriever for the time being, I think (i.e. deduplicate Packages files before passing them to anna). anna can't do it without poking into libdebian-installer internals. libdebian-installer ought to be fixed but the interface is death-by-abstraction and I'm certainly not confident in my ability to fix it correctly for a stable release update.

This bug was fixed in the package net-retriever - 1.21ubuntu2

---------------
net-retriever (1.21ubuntu2) intrepid; urgency=low

  * Deduplicate Packages files before passing them to anna (LP: #234486).
    Circumstances conspire to make this excessively difficult, including
    requiring net-retriever to become Architecture: any; this should really
    be done in libdebian-installer, but for the meantime that's even harder.
  * Fetch packages from security host if trying to fetch them from the main
    host fails (LP: #94398).

 -- Colin Watson <email address hidden> Fri, 30 May 2008 12:44:30 +0100

Accepted into -proposed, please test and give feedback here

ack. This fixed the hardy net install issue described above for me, with the exception of a simple module versions warning (due to -proposed). Can this be synced into main?

This may now be verified using the images here: http://archive.ubuntu.com/ubuntu/dists/hardy-proposed/main/installer-i386/current/

Just to comment further on my 'simple module warning':
The linux/initrd.gz in hardy-proposed/i386/current are 2.6.24-16

The error during unattended installation is:
No kernel modules were found. This probably is due to a mismatch between the kernel used by this version of the installer and the kernel version available in the archive....

You need to put "apt-setup/proposed=true" on the kernel command line, until such time as the -19 kernel lands in -updates. Sorry for forgetting to mention that earlier.

That last note from Colin Watson has restored peace and order to the world. Net installs are back online for me, Once again, I nominate for hardy-updates.

Will, thanks for testing!

Testing also confirmed in bug 238974.

I can also confirm that the solution is working by using the new netboot images and adding "apt-setup/proposed=true" to the kernel parameters.

Me too already managed to install a 8.04 via a local mirror successfully in the past, but also have problems now.

I replaced the original linux and initrd.gz on our provisioning server - taken from the netboot directory at the time - (where I can also confirm this libntfs-3g23-udeb error occurs: http://ubuntuforums.org/showthread.php?t=824576) by the hardy-proposed ones, and then also get 'No kernel modules were found...'.

1. Could you please tell me where to put exactly the apt-setup/proposed=true thing ? We use a self-made kind of auto-provisioning sytem - so this is a custom solution - but kernel stuff seems to be written here:
root@hb1590:/Storage/tftproot/kernels/x86/ubuntu-8.04# more /Storage/tftproot/pxelinux.cfg/01-00-0c-29-2f-ad-8b
default linux
prompt 1
timeout 30

label linux
    kernel kernels/x86/ubuntu-8.04/linux "apt-setup/proposed=true" <<<------- I added this manually, with or without quotes
    append initrd=kernels/x86/ubuntu-8.04/initrd.gz ksdevice=eth0 lang= text devfs=nomount ramdisk_size=7168 noipv6 ks=http://192.168.133.240/ks/cfg/ks-00-0c-29-2f-ad-8b-ubuntu-8.04.cfg
label local
    localboot 0x80
I still get the 'No kernel modules were found...'

2. When I 'continue' on this screen, eventually I get "No root file sytem is defined. Please correct this from the partitioning menu". I tried this on a physica Dell server AND on a virtual machine. Anyone had this error ? It does not happen with the 'old' initrd.gz and linux, if I try to 'continue' there.

 What should I try/do ? Thanks in advance.

You would have to add "apt-setup/proposed=true" (without the quotes) somewhere on the append line. Another option is to put the line in your preseed/kickstart file, I'm not sure about the syntax then.

 Jurgen:
> kernel kernels/x86/ubuntu-8.04/linux "apt-setup/proposed=true" <<<------- I added this manually, with or without quotes

label ubuntu-hardy-alternate-handsoff
        kernel ubuntu/hardy/alt/linux
        append initrd=ubuntu/hardy/alt/initrd.gz root=/dev/rd/0 rw locale=en_US console-setup/layoutcode=us netcfg/wireless_wep= netcfg/get_hostname= DEBCONF_DEBUG=5 tasksel:tasksel/first="ubuntu-standard, xubuntu-desktop" url=http://shaz/ubuntu/hardy/preseed-hardy-alt.cfg apt-setup/proposed=true --

got it?

installed without error - looks good.

I'm still seeming to have issues...

"No kernel modules were found error" on the latest kernel.

@ffm:
Have you added "apt-setup/proposed=true" without quotes to your kernel append line, or "d-i apt-setup/proposed boolean true" without quotes to your preseed script? Are you using a local mirror or a known-good upstream mirror with 2.6.24-19 already synced into -proposed?

@ffm:
Where did you get the "latest kernel" from?

root@shaz:/var/www/ubuntu/hardy/alt # md5sum linux initrd.gz
e933f99e7c5731f5637130f6dd8be8b9 linux
b4608e44d115d727a8845694b0c4eff2 initrd.gz

I just tried the 32-bit netboot.tar.gz from hardy proposed from our tftp server with the 'apt-setup/proposed=true' boot option and kickseed. The autoinstall proceeded fine without hanging up on any udebs.

@Will Nowak

Aha!

That'll teach me to read bug reports fully before commenting...

I reproduced that the original hardy netboot image failed on install, though I'm not sure the issue is due to this bug or bug 94398. I then verified that the hardy-proposed netboot image makes it to the point where it asks for an ssh password, when passed 'cli apt-setup/proposed=true anna/choose_modules=network-console' on the boot: line.

I have not yet completed a regular netboot install, but will do so.

Copied to hardy-updates.

Adding this comment to make this thread more searchable for others who have the same problem. Had this problem with an AMD64 netboot. Hardy-proposed linked above resolved my difficulty. I did not need to supply any boot options. The files where the installation fails for the original installer, as shown in the debug console (alt-F4), were libnewt0.52 and efi-modules.

Still having this issue with Hardy, except for me it's apt-mirror-setup freaking out. This is really frustrating because I can't find any info from the installer to tell me what is failing.

Adam Dorsey wrote:
> Still having this issue with Hardy, except for me it's apt-mirror-setup
> freaking out. This is really frustrating because I can't find any info
> from the installer to tell me what is failing.

I think you should open a new bug report. "unknown reasons" seems to be the
only similarity.

May help to boot with DEBCONF_DEBUG=5 and then look in /var/log/syslog.

if you see:

Package <something> is already installed and configured

then it will be more similar, but probably should still be a new bug report.

Carl K

I just experienced the apt-mirror-setup problem and filed Bug #244728

Adam, Brian, you need to use the installer image from hardy-updates, NOT the one from dists/hardy.

  http://archive.ubuntu.com/ubuntu/dists/hardy-updates/main/installer-amd64/current/images/
  http://archive.ubuntu.com/ubuntu/dists/hardy-updates/main/installer-i386/current/images/

Carl, it's overwhelmingly likely that it's the same bug in this case, and does not need a separate report.

Upgrading to the installer image from hardy-proposed solved the problem.