a) The problem was everywhere, but released everywhere else as part of
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2104165 . In the
course of that SRU, we were told not to SRU that changeset to Focal, but SRUing
a targeted fix to Focal might be more acceptable. Hence this bug.
b) I
I went through the procedures mentioned in both the description of this
issue, and the procedure laid out by Andreas in a previous comment. Both
succeed using the proposed version.
The scripts used as well as their output are in the attached tarball.
** Attachment added: "results.tar.gz"
http
** Description changed:
[ Impact ]
Cloud-init 25.1.2 changed installation of systemd-related packaging from
/lib to /usr/lib, which was suggested by lintian packaging warnings.[1]
- This change though is incompatible with debhelper version 13.6ubuntu1 in
- Jammy which now no longer "se
** Description changed:
- Does not affect: Noble, Oracular, Questing
+ [ Impact ]
- In cloud-init 25.1.2, changed systemd-related packaging from /lib TO /usr/lib
- which was suggested by lintian packaging warnings.[1]
+ Cloud-init 25.1.2 changed installation of systemd-related packaging from
+
Integration testing results are attached. Tests were run against EC2,
GCE, LXD containers, and LXD VMs. Reasons for failures are described in
failures.txt. Any necessary local reruns are captured in the *-rerun.txt
files.
** Attachment added: "jenkins_results.tar.gz"
https://bugs.launchpad.net
In an email on May 29, 2025, Christopher Patterson gave a +1 from
Azure's testing.
** Tags removed: verification-needed verification-needed-jammy
verification-needed-noble verification-needed-oracular
verification-needed-plucky
** Tags added: verification-done verification-done-jammy
verificati
** Summary changed:
- sru cloud-init (25.1.1 update) to focal, jammy, noble, oracular, and plucky
+ sru cloud-init (25.1 update) to focal, jammy, noble, oracular, and plucky
** Changed in: cloud-init (Ubuntu Focal)
Status: In Progress => Won't Fix
** Summary changed:
- sru cloud-init (25
** Description changed:
+ [ Impact ]
+
+ Deployments of images using cloud-init 24.04.1 are stuck at "rebooting"
+ if you use a bonded interface on the network that is used for the MAAS
+ management.
+
+ This happened because the MAAS datasource isn't often ready when cloud-
+ init starts sendin
This fix in 25.2~1g7a0265d3-0ubuntu1 is currently only available in
devel (questing).
For other stable Ubuntu releases, cloud-init has to be released through
the SRU process. This will be SRUed as 25.1.2. These have been uploaded
and are waiting for acceptance into the '-proposed' pockets. Once th
** Summary changed:
- sru cloud-init (25.1.2 update) to focal, jammy, noble and oracular
+ sru cloud-init (25.1.1 update) to focal, jammy, noble, oracular, and plucky
** Changed in: cloud-init (Ubuntu Plucky)
Status: Fix Released => In Progress
** Also affects: cloud-init (Ubuntu Questing
** Summary changed:
- sru cloud-init (25.1.1 update) to focal, jammy, noble and oracular
+ sru cloud-init (25.1.2 update) to focal, jammy, noble and oracular
** Description changed:
== Begin SRU Template ==
[Impact]
This release sports both bug-fixes and new features and we would like to
Thanks for the context Dave. I'll go ahead and remove the deprecation
message and file something in cloud-init upstream about better
supporting or documenting this use case.
** Changed in: cloud-init (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you
This is for identifying the filesystem that contains cloud-init metadata
at its root. Traditionally, cloud-init has used 'cidata' for this label.
Not using 'cidata' was recently deprecated because cloud-init's
generator only looks for the 'cidata' label. This can result in the
generator failing to
See https://github.com/canonical/cloud-init/pull/6167 for cloud-init
fix.
** Project changed: cloud-init => cloud-init (Ubuntu)
** Changed in: cloud-init (Ubuntu)
Importance: Unknown => Undecided
** Changed in: cloud-init (Ubuntu)
Status: Fix Released => New
** Changed in: cloud-init
The python bug was rolled back so I was able to get a successful build on focal:
https://launchpad.net/ubuntu/+source/cloud-init/24.4.1-0ubuntu0~20.04.2/+build/30422169
We should now be able to test focal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Oracular upgrading cloud-init 24.4.1-0ubuntu0~24.10.2 to
24.4.1-0ubuntu0~24.10.3:
- No errors on upgrade
- No errors on reboot
- `dpkg -l | grep cloud-init` shows no cloud-init-base, though `apt install
cloud-init-base` reports `Note, selecting 'cloud-init' instead of
'cloud-init-base'. cloud-in
** Description changed:
[ Impact ]
Cloud-init is currently broken on `do-release-upgrade` to plucky. In
plucky, cloud-init's packaging has been broken out into multiple binary
packages:
- cloud-init-base contains almost all of what used to be cloud-init
- minus some dependencies tha
Plucky, oracular, and noble packages have been uploaded.
** Changed in: cloud-init (Ubuntu Plucky)
Status: Triaged => Fix Committed
** Changed in: cloud-init (Ubuntu Oracular)
Status: New => Fix Committed
** Changed in: cloud-init (Ubuntu Noble)
Status: New => Fix Committed
** Changed in: cloud-init (Ubuntu Focal)
Status: New => Invalid
** Changed in: cloud-init (Ubuntu Jammy)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2092333
Tit
** Description changed:
+ [ Impact ]
+
+ Cloud-init is currently broken on `do-release-upgrade` to plucky. In
+ plucky, cloud-init's packaging has been broken out into multiple binary
+ packages:
+ - cloud-init-base contains almost all of what used to be cloud-init
+ minus some dependencies tha
*** This bug is a duplicate of bug 2092333 ***
https://bugs.launchpad.net/bugs/2092333
** This bug has been marked a duplicate of bug 2092333
package cloud-init-base 24.4-0ubuntu1 failed to install/upgrade: Versuch,
»/etc/cloud/cloud.cfg« zu überschreiben, welches auch in Paket cloud-init
> the effect being slightly different on Noble than on plucky?
Why is the effect different?
Agreed though. The change in 2104238 should also address this issue.
Cloud-init has removed DSA support.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Zachary, are you saying they're breaking while using the cloud-init
currently in proposed (24.4.1-0ubuntu0~.2)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100963
Title:
cloud-init fails with MAA
At the very least, this will result in IPv6 openstack instances failing to boot:
https://github.com/canonical/cloud-init/blob/main/cloudinit/sources/DataSourceOpenStack.py#L78
I think this needs to be treated as a critical issue.
--
You received this bug notification because you are a member of
It looks like the cause of our build failure is due to a recent change
in Focal's python.
https://bugs.launchpad.net/ubuntu/+source/python3.8/+bug/2103454
Does that mean our package needs to wait until that can be fixed?
--
You received this bug notification because you are a member of Ubuntu
B
Public bug reported:
It appears 3.8.10-0ubuntu1~20.04.16 fixed
https://github.com/python/cpython/issues/105704 . However, in doing so,
it also broke IPv6 zone parsing.
The following used to work on focal:
>>> from urllib.parse import urlparse
>>> urlparse('http://[fe80::1ff:fe23:4567:890a%25eth0]
I'm looking into the problem. Something appears to have changed in the
sbuild environment (or deps) that is causing some unrelated
failures...it now also fails when I try to build the previous release
that succeeded previously.
--
You received this bug notification because you are a member of Ubu
** Description changed:
This integration test is currently failing on plucky:
https://github.com/canonical/cloud-init/blob/a136a979dd5a5084f71f5def5abf6d80d7cc263a/tests/integration_tests/test_networking.py#L313
This test will launch an ec2 instance, attach a 2nd NIC, and then assign
t
** Changed in: cloud-init (Ubuntu Plucky)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100963
Title:
cloud-init fails with MAAS since Feb 4 update
To
** Description changed:
+ [Impact]
+
+ Cloud-init 24.4.1 included a change[1] that results in a traceback on MAAS
systems. This is because the cloud-init MAAS datasource code wraps behavior
provided by the readurl() helper function, so because the readurl() helper
function signature changed bu
Unfortunately, no, I have no ETA.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100963
Title:
cloud-init fails with MAAS since Feb 4 update
To manage notifications about this bug go to:
https://bu
networkctl output:
root@ip-192-168-11-242:/home/ubuntu# networkctl status
● Interfaces: 1, 2, 3
State: routable
Online state: online
Address: 192.168.11.242 on ens5
192.168.12.6 on ens6
** Description changed:
This integration test is currently failing on plucky:
https://github.com/canonical/cloud-init/blob/a136a979dd5a5084f71f5def5abf6d80d7cc263a/tests/integration_tests/test_networking.py#L313
This test will launch an ec2 instance, attach a 2nd NIC, and then assign
t
networkd debug logs attached from after reboot on plucky
** Attachment added: "networkd_debug_plucky"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2101860/+attachment/5864048/+files/networkd_debug_plucky
--
You received this bug notification because you are a member of Ubuntu
Bu
Also adding netplan and systemd here as the rendered networkd config
doesn't change, and the netplan apply call is racy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2101860
Title:
Different networ
networkd debug logs attached from after reboot on oracular
** Attachment added: "networkd_debug_oracular"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2101860/+attachment/5864049/+files/networkd_debug_oracular
** Also affects: systemd (Ubuntu)
Importance: Undecided
Stat
It appears Plucky is missing the proper rule:
root@ip-192-168-11-242:~# ip rule
0: from all lookup local
32765: from 192.168.15.230 lookup 101 proto static
32766: from all lookup main
32767: from all lookup default
Compared to Oracular:
root@ip-192-168-1-227:/usr/lib/systemd/network# ip ru
Public bug reported:
This integration test is currently failing on plucky:
https://github.com/canonical/cloud-init/blob/a136a979dd5a5084f71f5def5abf6d80d7cc263a/tests/integration_tests/test_networking.py#L313
This test will launch an ec2 instance, attach a 2nd NIC, and then assign
two (total) I
> When removing the "use-routes" dhcp-overrides for ens6 and running
"netplan apply" it seems to be working.
The default for this is true, so unless the documentation is wrong, I
don't think that changing this is actually doing anything.
There is certainly some racy behavior though. Using a scrip
Plucky routes:
ubuntu@ip-192-168-11-242:~$ ip route
default via 192.168.0.1 dev ens5 proto dhcp src 192.168.11.242 metric 100
default via 192.168.0.1 dev ens6 proto dhcp src 192.168.12.6 metric 1003 mtu
9001
192.168.0.0/20 dev ens5 proto kernel scope link src 192.168.11.242 metric 100
192.168.0
Yes, we'll get it backported ASAP.
** Changed in: cloud-init (Ubuntu)
Status: New => Triaged
** Changed in: cloud-init (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because y
Is it possible to get the resulting tarball from `cloud-init collect-
logs`?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100620
Title:
cloud-init not importing ssh keys
To manage notifications a
In addition to the regression tests posted above, tests for this
particular feature were tested on package build against a fake IMDS.
** Tags removed: verification-needed verification-needed-focal
verification-needed-jammy verification-needed-noble verification-needed-oracular
** Tags added: veri
Regression test results on EC2. Jammy failures are due to test changes
for netplan that haven't yet been SRUed.
** Attachment added: "test_results_2094858.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2094858/+attachment/5860861/+files/test_results_2094858.tar.gz
--
You r
This should be fixed in cloud-init version 25.1-0ubuntu2 .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098988
Title:
cloud-init datasource failure on Azure
To manage notifications about this bug
** Changed in: cloud-init (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098988
Title:
cloud-init datasource failure on Azure
To manage notifications
** Tags removed: verification-needed verification-needed-focal
verification-needed-jammy verification-needed-noble verification-needed-oracular
** Tags added: verification-done verification-done-focal
verification-done-jammy verification-done-noble verification-done-oracular
--
You received thi
Test results
** Attachment added: "test_results_2097319.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2097319/+attachment/5860234/+files/test_results_2097319.tar.gz
** Tags removed: verification-needed verification-needed-focal
verification-needed-jammy verification-neede
Test results
** Attachment added: "test_results_2094179.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2094179/+attachment/5860136/+files/test_results_2094179.tar.gz
** Tags removed: verification-needed verification-needed-focal
verification-needed-jammy verification-neede
Test results attached
** Attachment added: "test_results_2094208.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2094208/+attachment/5859269/+files/test_results_2094208.tar.gz
** Tags removed: verification-needed verification-needed-focal
verification-needed-jammy verificat
Thanks for the offer to cloud-init! We'll likely take you up on that
soon.
It looks like your bug was something introduced in the last release, but it was
a particularly instance of a more general change in cloud-init. Cloud-init will
exit 2 when it hits recoverable errors. This is new behavior
Test results ensure /var is mounted are attached for each series.
** Attachment added: "test_results_2097441.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2097441/+attachment/5859141/+files/test_results_2097441.tar.gz
** Tags removed: verification-needed verification-neede
Test results attached. Tested cases where bootcmd are included and not
included in user data representing the cases that previously resulting
in waiting vs not waiting.
** Attachment added: "test_results_2094149.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2094149/+attachm
** Description changed:
[ Impact ]
There was an upstream change that moved
`RequiresMountsFor=/var/lib/cloud` from cloud-init-local.service to
cloud-init-main.service. Since cloud-init-main.service was patched out
of stable downstreams, this `RequiresMountsFor` line was accidentally
Thanks Jarrett, we'll get this fixed soon.
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Critical
** Changed in: cloud-init (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
** Description changed:
[ Impact ]
On Digital Ocean and some bare metal instances, changes introduced in
e30549e8 are causing older instances to fail to boot. While the cloud-
init team cannot reproduce the exact scenario, we have received enough
reports that we believe it prudent rev
** Description changed:
[ Impact ]
On Digital Ocean and some bare metal instances, changes introduced in
e30549e8 are causing older instances to fail to boot. While the cloud-
init team cannot reproduce the exact scenario, we have received enough
reports that we believe it prudent rev
** Description changed:
[ Impact ]
There was an upstream change that moved
`RequiresMountsFor=/var/lib/cloud` from cloud-init-local.service to
cloud-init-main.service. Since cloud-init-main.service was patched out
of stable downstreams, this `RequiresMountsFor` line was accidentally
** Description changed:
[ Impact ]
There was an upstream change that moved
`RequiresMountsFor=/var/lib/cloud` from cloud-init-local.service to
cloud-init-main.service. Since cloud-init-main.service was patched out
of stable downstreams, this `RequiresMountsFor` line was accidentally
** Description changed:
[ Impact ]
- Originally reported upstream[1], an issue with systemd ordering caused by a
previous patch affects focal, jammy, and noble and causes NoCloud to be
undetected in some cases (identified when using LVM).
-
+ There was an upstream change that moved
+ `R
** Also affects: cloud-init (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notificat
For your other questions:
> Did you have any specific reasoning to not implement an escape hatch
to this infinite loop? Is it extra risk? Was it deemed unlikely, as
clouds would "never" have the metadata service return 503 for too long?
Or did you consider a stuck instance in a retry loop better t
That PR is not specific to EC2. If affects all datasources in that it
affects the response handling of every HTTP response that doesn't have
special error handling defined for it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
> Even so, if there is a script collecting this metric out there
somewhere, and just checking if port 22 is reachable, it will just see
this potential extra delay.
If we were to get a bug along these lines, I would close it as invalid
because the alternative is for the instance to not boot at all.
Our old documentation had this:
https://docs.cloud-init.io/en/24.1/development/module_creation.html
including the line "__doc__ = get_meta_doc(meta)".
That line was included in every single module for generating our
upstream documentation. This ceased in 24.2. In 24.2, this function had
no more m
> Where in this diff[1] is the change only impacting "Hetzner"?
Strictly, it's not, but that's the only datasource we know of that is
affected.
In early boot, before networking has started, cloud-init usually sets up
an Ephemeral DHCP connection so that it connect to the IMDS and then
tears that
Yes to your summary.
2094857 is unrelated. A 503 should not be ignored anywhere after this
change.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2094858
Title:
Cloud-init fails on AWS if IMDSv2 ret
No, documentation will not be produced the same, but that has been true
since 24.2
The documentation generation is for generating upstream docs at
https://docs.cloud-init.io/en/latest/ . I wouldn't really expect a user
with custom modules to be doing this. That would mean hosting an
entirely separ
> and still not fixed in 24.4.1
The function was only used in generating public documentation. It is no
longer used for that purpose, hence why we replaced it with a stub in
24.4.1. Why do you say still not fixed?
> Why was that method removed, and why isn't there a phasing out for it,
instead of
DataSourceExoscale.py was changed to log an error because that was one
of the few datasources that previously didn't log an error if the
process described in this Impact failed. Essentially this moved an error
log out from a section of code that we're ok with failing to a later
stage where we care
Andreas, I have updated the Impact and Test Plan accordingly. Please let
me know if you still have additional questions.
** Description changed:
[ Impact ]
- Cloud-init handles 503's generically as any other errors even though it
- is a message from the server of when and how to retry later.
Public bug reported:
[ Impact ]
Cloud-init handles 503's generically as any other errors even though it
is a message from the server of when and how to retry later. This is
issues within AWS.
[ Test Plan ]
Boot an instance. Observe a 503 from the IMDS when contacting the
metadata service. Ensur
Public bug reported:
[ Impact ]
Cloud-init checks for IMDS connectivity before setting up an ephemeral
network. In 24.4, this code was refactored to use a function that
supported multiple URLs rather than just one. If this function fails, it
logs an error, causing cloud-init to exit 2. On Hetzner
** Also affects: cloud-init (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Oracular)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubu
** Summary changed:
- cloud-init 24.4 prevents Ubuntu 20.04 Digital Ocean droplet from booting
+ Changes to cloud-init's systemd-networkd-wait-online interactions causing
boot failure
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Public bug reported:
[ Impact ]
In cloud-init 24.4, custom signal handling code was added to log errors
when cloud-init received signals that resulted in cloud-init's death.
However, cloud-init legitimately needs to die when cloud-init triggers a
reboot, so these handlers caused unexpected errors
Public bug reported:
[ Impact ]
In 24.4, cloud-init made changes to document generation that removed the
need for a function called 'get_meta_doc()' that was used in document
generation. This resulted in a breaking change for any custom drop-in
modules following older best practices (e.g., https:
** Changed in: cloud-init (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2094149
Title:
cloud-init 24.4 prevents Ubuntu 20.04 Digital Ocean droplet from
booti
Public bug reported:
[ Impact ]
On Digital Ocean and some bare metal instances, changes introduced in
e30549e8 are causing older instances to fail to boot. While the cloud-
init team cannot reproduce the exact scenario, we have received enough
reports that we believe it prudent revert this change
Can I get some input from a subiquity dev on this? Cloud-init has both
this and https://bugs.launchpad.net/ubuntu/+source/cloud-
init/+bug/2092713 which is essentially the same bug but upgrading to a
different version of cloud-init.
Both are happening on a noble desktop install when upgrading from
** Changed in: cloud-init (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080150
Title:
Password Reset broken with CloudstackDatasource
To manag
** Tags removed: verification-needed verification-needed-focal
verification-needed-jammy verification-needed-noble verification-needed-oracular
** Tags added: verification-done verification-done-focal
verification-done-jammy verification-done-noble verification-done-oracular
--
You received thi
Chris Patterson from Microsoft confirmed via email that SRU testing
looks good on their end.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089577
Title:
sru cloud-init (24.4 update) focal, jammy,
Cloud-init integration test result are attached. This includes Jenkins
runs for tests on focal, jammy, noble, and oracular on Azure, Ec2, Gce,
Lxd container, and Lxd VMs using generic and minimal images (where
applicable). Known failures are explained in `failures.txt` and
transient failures have b
While GH-5849 could have the same root cause, at first glance, the code
paths appear to be different. I think the cloud-init part of this issue
was closed prematurely. I'm setting this to incomplete until we can get
the full logs.
** Changed in: cloud-init (Ubuntu)
Status: Invalid => Incomp
Is it possible to get the full cloud-init logs as specified in
https://docs.cloud-init.io/en/latest/howto/bugs.html#collect-logs ? The
result is a tarball that also includes the cloud-init logs. The posted
'Full logs' link does not link to the full logs.
--
You received this bug notification beca
** Also affects: cloud-init (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu
** Description changed:
== Begin SRU Template ==
[Impact]
This release sports both bug-fixes and new features and we would like to
make sure all of our supported customers have access to these
improvements. The notable ones are:
- TODO
+ - feat(oracle): add true single stack ipv6 supp
Public bug reported:
== Begin SRU Template ==
[Impact]
This release sports both bug-fixes and new features and we would like to
make sure all of our supported customers have access to these
improvements. The notable ones are:
TODO
[Test Case]
The following development and SRU process was followe
** Changed in: cloud-init (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2079224
Title:
sru cloud-init (24.3.1 update) focal, jammy and noble
To man
> avoiding sshd_config.d all together
Why? Isn't this the entire point of the .d directory? The package
provides a default configuration. If another package or service (like
cloud-init) wants to change it, they should be dropping in an override
file. If cloud-init changes the config file it's less
This is fixed in https://github.com/canonical/cloud-init/pull/5701 and
will be available in cloud-init version 24.4
** Also affects: cloud-init (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu Noble)
Status: New => Fix Committed
** Changed in: c
** Description changed:
- I Oracular 24.10, cloud-init 24.3.1 renamed cloud-init.service to cloud-
- init-network.service as part of the single-process mode support. This
- is only introduced in Oracular and not applicable to any stable releases
- before Oracular.[1]
+ In Oracular 24.10, cloud-in
Hi Danilo. The PPA works for me and fixes the problem for me. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078009
Title:
"netplan apply" not applying after cloud-init hotplug
To manage no
This bug is fixed in cloud-init 24.3, which should be hitting the Ubuntu
-proposed pocket soon. After being verified in -proposed, it will be
released to -updates.
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a membe
This should be fixed as of https://github.com/canonical/cloud-
init/pull/5619 and should be present in cloud-init version 24.3.
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Eh sorry, I think I misspoke. On a new python version we clear the
object pickle, not the entire instance cache. Ignore my previous
comment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2075968
Title
I see `"lock_passwd": true` (a cloud-init default) in the instance-data-
sensitive.json file. Was the account manually unlocked at some point?
If so, when doing a release upgrade, cloud-init will see a new python
version, clear it's cache, then run as if it was first boot again.
--
You received
Got email confirmation from Azure folks that what is in proposed passes
their testing.
** Tags removed: verification-needed verification-needed-focal
verification-needed-jammy verification-needed-noble
** Tags added: verification-done verification-done-focal
verification-done-jammy verification-
Attached are the results of cloud-init integration testing for 24.2.
Integration tests were run on Focal, Jammy, and Noble for clouds Azure,
EC2, GCE, LXD Container, and LXD VM along with any necessary reruns.
Additionally, the Curtin cloud-init SRU job was also run and attached.
Reasons for fai
1 - 100 of 302 matches
Mail list logo
