Chad Smith

Confirmed with the following procedure on lxd noble images with builddate 20240220: ## test script ``` #/bin/sh set -ex lxc launch ubuntu-daily:noble nn lxc exec nn -- cat /etc/cloud/build.info lxc...

This PR is really waiting on closeout of the known 24.1.1 issues we want to sync. I'm recusing myself from review here as I am leaving on PTO for a...

The issue I'm seeing, and neglected to think about before this effort, is that our generator time-frame remains unaware of any system config run_path. This then leaves cloud-init in a...

>> It is up to you whether we go forward with the current approach (given the points raised above), or try for a more complete run_dir-everywhere approach which depends on...

> All of these are systemd-specific code-paths, and [systemd explicitly requires an ephemeral /run](https://github.com/systemd/systemd/blob/8959e17d736fbdbaf7cd912f35d23ced2e261327/README#L414C35-L414C39) directory, so I don't think there is anything to fix related to these three points. Good...

Still waiting on SRU resolution for landscape-client before this lands.

> @blackboxsw , looks like the last comment on that bug is from 2023-10-20 . Do we expect that to be SRUed anytime soon? Yep. I had circled back with...

Checked again on this landscape-client SRU. All tests are verified, SRU review queue is saturated given demand for Noble release reviews. Giving this another week to allow the Noble release...

chifac08 looks like landscape-client published yesterday. I just validated your PR works great on both Ubuntu focal and jammy with the newly published landscape-client --is-registered param. Finally landing this without...

Sorry, I'm misunderstanding the problem here. cloud-init seems to be told to use DHCP on the primary interface in DigitalOcean droplets and it obtains a private IP address, but the...