Package: fai-client
Version: 3.2.20
Severity: normal

Output of fai 3.2.20:

| [....]
| 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
| Calling debootstrap squeeze --arch i386 --exclude=dhcp-client,info 
/srv/grml-live/grml_chroot http://ftp.de.debian.org/debian/
| I: Retrieving Release
| I: Retrieving Packages
| I: Validating Packages
| I: Resolving dependencies of required packages...
| I: Resolving dependencies of base packages...
| I: Found additional required dependencies: libdb4.7
| I: Checking component main on http://ftp.de.debian.org/debian...
| I: Retrieving adduser
| I: Validating adduser
| I: Retrieving apt
| [...]
| I: Configuring tasksel...
| I: Base system installed successfully.
| Error in task extrbase. Traceback: task_error task_extrbase task 
task_dirinstall task task_action task main
| FATAL ERROR. Installation stopped.
| umount: /srv/grml-live/grml_chroot/dev: not mounted

Doesn't happen with fai 3.2.17~lenny1 though:

| [...]
| I: Base system installed successfully.
| Exit code task_extrbase: 801
| Calling task_mirror
| Calling task_debconf
| Reconfiguring package passwd
| Calling task_prepareapt
| Calling hook: updatebase.GRMLBASE
| OK
| updatebase.GRMLBASE  OK.
| Calling task_updatebase
| [...]

Manually invoking debootstrap:

# debootstrap --arch i386 --exclude=dhcp-client,info squeeze /srv/debootstrap 
http://ftp.de.debian.org/debian/
[...]
I: Base system installed successfully.
# echo $?
0

The "set STOP_ON_ERROR to 700" introduced in fai 3.2.18 seems to be
the reason for this problem. I don't find any relevant changes in the
debootstrap code but I'm wondering why task_extrbase returns 801
even though debootstrap seems to work fine. Any hints/ideas?

regards,
-mika-



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to