It then waits and eventually creates some keys. Then login appears. Wrong/default hostname though.
Then cloud init says en_US.UTF-8... done which means it's not ignoring the file completely (I guess).
Then it regenerates a machine id and prints fingerprints for user debian.
Later it says no authorized ssh keys fingerprints found for user debian
A little confused I am wondering - are things broken?
Then I found issue #138 and realized that all that was missing was the #cloud-config shebang.
It would be fantastic if this could be checked by the script - and not just that's a valid yml file.
Running
bootconf
gets appliedusing this file
the cloud init gives problems.
When booting it's strange that eth0 is not up. Then the cloud prints
It then waits and eventually creates some keys. Then login appears. Wrong/default hostname though. Then cloud init says
en_US.UTF-8... done
which means it's not ignoring the file completely (I guess). Then it regenerates a machine id and prints fingerprints for userdebian
. Later it saysno authorized ssh keys fingerprints found for user debian
A little confused I am wondering - are things broken?
Then I found issue #138 and realized that all that was missing was the
#cloud-config
shebang.It would be fantastic if this could be checked by the script - and not just that's a valid yml file.