I've verified each of trusty,yakkety and xenial by modifying the user-data in the script and then running
bash -c 'set -o pipefail; for i in "$@"; do ./prepare-1688606.sh $i 2>&1 | tee $i.log || break; ( cd $i && ./boot >../$i-boot.log 2>&1 </dev/null ); done' -- trusty xenial yakkety
I'll attach <release>.log and <release>-boot.log for each.
The modification to the script was just to add the following into the user-data. you can see its output in the logs.
runcmd: - ['sh', '-c', 'echo ===================================='] - ['sh', '-c', 'echo === /proc/mounts ===; cat /proc/mounts'] - ['sh', '-c', 'echo === /proc/cmdline === ; cat /proc/cmdline'] - ['sh', '-c', 'echo === df -h ===; df -h'] - ['sh', '-c', 'echo === free ===; free'] - ['sh', '-c', '( sleep 10 ; poweroff )</dev/null >/dev/null 2>&1 &'] - ['sh', '-c', 'echo ====================================']
I've verified each of trusty,yakkety and xenial by modifying the user-data in the script and then running
bash -c 'set -o pipefail; for i in "$@"; do 1688606. sh $i 2>&1 | tee $i.log || break;
./prepare-
( cd $i && ./boot >../$i-boot.log 2>&1 </dev/null );
done' -- trusty xenial yakkety
I'll attach <release>.log and <release>-boot.log for each.
The modification to the script was just to add the following into the user-data. you can see its output in the logs.
runcmd: ======= ======= ======= ======= ='] ======= ======= ======= ======= =']
- ['sh', '-c', 'echo =======
- ['sh', '-c', 'echo === /proc/mounts ===; cat /proc/mounts']
- ['sh', '-c', 'echo === /proc/cmdline === ; cat /proc/cmdline']
- ['sh', '-c', 'echo === df -h ===; df -h']
- ['sh', '-c', 'echo === free ===; free']
- ['sh', '-c', '( sleep 10 ; poweroff )</dev/null >/dev/null 2>&1 &']
- ['sh', '-c', 'echo =======