as you, sadly, have new naming conventions for your images, the script had an error, as i called it via terraform, the script got stuck so hard that i had to kill the terraform process, even a ctrl-x or ctrl-c have not helped.
terraform was stuck at:
i had to add a logoutput to my terraform which outputs the exactly command and run it manually on the system to finally see:
which i debugged to your new file naming scheme.
running installimage with -a (or maybe a new flag like --no-interaction or --batch) should never lead to a gui showing the error but to a non-zero exit code an an error message to std-err.
would be really helpful and safe time.
it would be really nice if you could add a symlink following the previous naming scheme. in general a more stable naming scheme would be awesome.
i use install image via terraform with the
-a
flag to provision my images with the following commandas you, sadly, have new naming conventions for your images, the script had an error, as i called it via terraform, the script got stuck so hard that i had to kill the terraform process, even a
ctrl-x
orctrl-c
have not helped.terraform was stuck at:![image](https://user-images.githubusercontent.com/649209/137981571-f87d79ed-dc66-40c2-869c-6da1007d09a6.png)
i had to add a logoutput to my terraform which outputs the exactly command and run it manually on the system to finally see:
which i debugged to your new file naming scheme.
running installimage with
-a
(or maybe a new flag like --no-interaction or --batch) should never lead to a gui showing the error but to a non-zero exit code an an error message to std-err.would be really helpful and safe time.
it would be really nice if you could add a symlink following the previous naming scheme. in general a more stable naming scheme would be awesome.
debian buster should not be called debian stable any more.
something like the following would be really helpful