Chad Smith
Chad Smith
> you basically have two unit files with conflicting requirements. cloud-init.service want's to start before sysinit.target and firewalld.service after sysinit.target. Both are tied together via network-pre.target. Why cloud-init.service needs to...
This is also likely represented by this upstream cloud-init bug https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1956629
adding 24.3 milestone, as we don't necessarily want to block 24.2 on this development.
Also a general security question here. Given that user-data and vendor-data likely contains potentially sensitive information and Aeza.net's instance metadata endpoint is providing content over http that appears to be...
Hi @cofob, I don't see that your github username has signed the cloud-init's [Contributor License Agreement](https://cloudinit.readthedocs.io/en/latest/development/first_PR.html#sign-the-cla). So that I can enable CI on this PR and move toward merging this...
@cofob if the proposed changes work for you, I think the final thing we'd need (once we agree on the approach for how to address `util.read_seeded`) would be to have...
Ping @cofob. I think this PR needs a `git rebase upstream/main` to ensure it has visibility to the incompatible changes in util.read_seeded which surfaces a 4-tuple return value. Let us...
Confirmed this on LXD: ``` cat > ud.yaml
[cloud-init.tar.gz](https://github.com/canonical/cloud-init/files/11848862/cloud-init.tar.gz)
[Debian docs for locale](https://wiki.debian.org/Locale)