Package: fai-client Version: 3.2.1 Severity: normal
The dirinstall feature does not return with an exitcode != 0 in many situations (IIRC I never saw dirinstall exiting with something else than 0 at all ;-)). As it just happened again and I've the logs available: # fai -C /etc/grml/fai -cGRMLBASE,I386 -u grml dirinstall /srv/grml-live/grml_chroot [...] Using configuration files from /etc/grml/fai Calling task_setup FAI_FLAGS: Calling task_defclass List of all classes: GRMLBASE I386 Calling task_defvar ++ FAI_ALLOW_UNSIGNED=1 ++ CONSOLEFONT= ++ KEYMAP=us-latin1 ++ UTC=yes ++ TIMEZONE=Europe/Vienna ++ ROOTPW=x Calling task_action FAI_ACTION: dirinstall Calling task_dirinstall Installing into directory /srv/grml-live/grml_chroot Calling task_extrbase Unpacking Debian base archive No base.tgz found. Calling debootstrap. Creating base system using debootstrap version 0.3.3.2etch1 Calling debootstrap etch /srv/grml-live/grml_chroot http://localhost:9999/debian I: Retrieving Release E: Failed getting release file http://localhost:9999/debian/dists/etch/Release touch: cannot touch `/srv/grml-live/grml_chroot/etc/fstab': No such file or directory Calling task_mirror Calling task_debconf chroot: cannot run command `mktemp': No such file or directory [...] => So the debootstrap command completely failed in my example but dirinstall tried to resume with normal operations. Another problem I could reproduce several times is the installation of software inside the chroot -> if installation of a package fails then dirinstall exits with return code 0 as well. I wrote a simple patch to fix the later issue, check out http://grml.org/tmp/fai_dirinstall_check.diff for details. I think we should check out this issue in more detail together so we can provide a nice way how to check for errors and exit accordingly. As usual please feel free to ping me on IRC if you need any further information, feedback, testing,... I'd work on patches as well of course as soon as I know what's your favourite solution. :) regards, -mika- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
