Source: fai Version: 5.7.2 Severity: grave There seems to be no way to make hooks abort the run. I explicitely made a hook always fail and it always continued:
| partition.GRUB_CLOUD_AMD64 FAILED with exit code 1. | Skipping task_partition | Calling hook: mountdisks.CLOUD | No fstab file /var/log/fai/debian/install-20190104_050000/fstab found. | mountdisks.CLOUD FAILED with exit code 117. | Skipping task_mountdisks | Calling task_extrbase | ftar: No matching class found in /var/tmp// The exit value is reported via lib/check_status, but never saved. Another problem: fai-do-scripts wants to do "RC+100". As exit values are a value from 0 to 255, this can overflow. Bastian -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
