Hi Diego,
I remember I had this issue years ago, and I may not had fixed it
correctly. Using the FAI flag reboot we cannot cover three different
cases. In my own config space I've added a line into hooks/savelog.LAST.sh
savelog.LAST.sh:
.
.
.
if [ -s $errfile ]; then
echo "ERRORS found in
> On Tue, 31 May 2022 10:56:50 +0200, Diego Zuccato
> said:
> Reading man page for fai-make-nfsroot it seems 'FULL' install is the
> default. But after having troubles adding Salt repository (could not
> verify server certificate), I noticed that ca-certificates (installed
Hi Robert.
Then it seems the docs are outdated. Not a big issue, even if the
described behaviour would be more useful (automatic reboot if no errors,
wait for confirmation in case of errors unless 'reboot' is given). :)
BYtE,
Diego
Il 31/05/2022 12:23, Robert Markula ha scritto:
Hi Diego,
Hi Diego,
Moreover, at the end of the install, after saying there were no
errors, FAI asked to press ENTER to reboot, but IIUC that should me
automatic, w/o manual confirmation: docs at
https://fai-project.org/fai-guide/#_a_id_faiflags_a_fai_flags says
that "If no errors occurred, the client
Hello all.
FAI noob here, please be patient :)
Reading man page for fai-make-nfsroot it seems 'FULL' install is the
default. But after having troubles adding Salt repository (could not
verify server certificate), I noticed that ca-certificates (installed
only in FULL nfsroot) was not
