On Sun, Aug 4, 2019 at 1:21 PM Steve Dodd <email address hidden>
wrote:
> Having just been battling with this - config-set-passwords is run
> relatively late (config stage), which seems to mean the network has to be
> up properly before it is executed..
> if you get dropped into maintenance mode, or manually edit the image to
> provide a log in, "cloud-init status" and "cloud-init analyze show" will
> tell you what is going on.
>
> TL;DR : relying on "password:" to create a user account you can log in
> with to diagnose network problems, isn't going to work :/
>
Sorry for being unclear; I was suggesting to modify the image _before_ your
boot,
This drops you into a bash shell inside the cloud-image that's not yet
booted, from here you can
set a root password with:
4. passwd
Then type 'exit' to leave the chroot, and then boot this modified image
along with your
cloud-config or anything else. Then you can login as root with the
password you set.
And collect some debugging data.
On Sun, Aug 4, 2019 at 1:21 PM Steve Dodd <email address hidden>
wrote:
> Having just been battling with this - config- set-passwords is run
> relatively late (config stage), which seems to mean the network has to be
> up properly before it is executed..
> if you get dropped into maintenance mode, or manually edit the image to
> provide a log in, "cloud-init status" and "cloud-init analyze show" will
> tell you what is going on.
>
> TL;DR : relying on "password:" to create a user account you can log in
> with to diagnose network problems, isn't going to work :/
>
Sorry for being unclear; I was suggesting to modify the image _before_ your
boot,
# on your arm64 host cloud-images. ubuntu. com/daily/ server/ bionic/ current/ bionic- server- cloudimg- arm64.img
1. wget
http://
2. sudo apt install cloud-image-utils callback bionic- server- cloudimg- arm64.img -- chroot
3. sudo mount-image-
_MOUNTPOINT_ /bin/bash
This drops you into a bash shell inside the cloud-image that's not yet
booted, from here you can
set a root password with:
4. passwd
Then type 'exit' to leave the chroot, and then boot this modified image
along with your
cloud-config or anything else. Then you can login as root with the
password you set.
And collect some debugging data.
> -- /bugs.launchpad .net/bugs/ 1818197 18.04-server- cloudimg- arm64.img often fails to set the cloud- /bugs.launchpad .net/cloud- images/ +bug/1818197/ +subscriptions
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> ubuntu-
> localds password under QEMU
>
> To manage notifications about this bug go to:
> https:/
>