DisasteR: difficult to say if it was a change from the cloud-images,
cloud-init or other package without access to the jammy instance. But in
any case, write_files, bootcmd and runcmd are config modules that can
break the system in multiple ways as they give total control to the user
and they have
@aciba I can confirm that adding `defer: true` on my write_file resolve
the problem.
Can you explain if this is caused by a change in cloud-init or if i was
just lucky from the start .. ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'll try that.
but that worked with previous cloud-init versions -_- is that a new option ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049860
Title:
cloud-init cloud-config for ssh broken in
Hi DisasteR, thanks for attaching the logs.
ssh_pwauth gets handled by the set_passwords config module, which runs
as part of the cloud-config stage.
The problem is that cloud-config and cloud-final stages didn't run
because cloud-init is instructed to be disabled.
Some stanza in your
I verified it and everything is ok.
Here is the collected logs.
** Attachment added: "cloud-init.tar.gz"
https://bugs.launchpad.net/cloud-images/+bug/2049860/+attachment/5764105/+files/cloud-init.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi @DisatesR.
In addition to John's comment, collecting and sharing cloud-init's
logs[1] (making sure no sensitive data is attached) might help us to
triage what's happening.
[1]https://cloudinit.readthedocs.io/en/latest/howto/bugs.html#collect-
logs
--
You received this bug notification
@DisatesR : if you're not seeing a 50-cloud-init.conf file, it indicates
to me that cloud-init is failing to parse the cloud_init configuration
properly, and thus not adding the required configuration to
/etc/ssh/sshd_config.d/
could you provide your entire cloud config? you can also use
Hi @jchittum
I made some test today using the daily build from 20240403 and same
problem.
cloud init version is 23.4.4-0ubuntu0~22.04.1
ssh_pwauth is present in /var/run/cloud-init/combined-cloud-config.json
and value is true.
root@r-bsz-test-001:/# grep ssh_pwauth
@jchittum
I setup user with the same parameters and i also generate passwords with
mkpasswd --method=SHA-512 but i cannot ssh using password on the listed
images.
It work as expected with the old one release-20231211.
I looked the log but didn't find any error.
And password is working locally.
Tested working on the image from http://cloud-
images.ubuntu.com/releases/jammy/release-20240319/
$ ssh -o "UserKnownHostsFile=/dev/null -o CheckHostIP=no StrictHostKeyChecking
no" jchittum@0.0.0.0 -p
The authenticity of host '[0.0.0.0]: ([0.0.0.0]:)' can't be established.
ED25519
@jchittum --
I use Jammy images from cloud-images.ubuntu.com.
I tested multiple daily images from 2024 like :
20240315.1
20240319
And i cannot connect to the vm by ssh using password with `ssh_pwauth:
True`
Cloud init configuration still set `passwordauthentication no` in
@DisasteR -- could you be more specific? Which images are you seeing
this in? which cloud, which download from `cloud-images.ubuntu.com`?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049860
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: livecd-rootfs (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049860
Hi,
Looks like this bug is still present in daily Jammy cloud images.
Any idea when this will be available in new daily builds ?
Regards,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049860
14 matches
Mail list logo
