I hit this on my desktop after updating to Plucky.
> As a workaround until the issue is fixed, it is safe to do:
>
> `test -f /etc/logrotate.d/cloud-init-base && rm -v
> /etc/logrotate.d/cloud-init`
>
> to manually clean the duplicated logrotate config.
This appeared to resolve the error. Howeve
> The reason seems due to
There is a known cloud-init packaging issue in the upgrade path which
causes this - the team is aware of it and working on a solution.
However, cloud-init is a systemd service. How could that be the root
cause of your initramfs failure?
The initramfs issue that was origi
> If it's not worse, I believe we can proceed with the SRU, but by
keeping this bug open and with the appropriate tag. What do you think?
I agree with your assessment. I think that it's not worse, but like you
said it's not completely fixed.
Since 25.1 downstream release is just around the corner
> Comment #10 tested this SRU on jammy and noble. Looks like in noble
it's not fully fixed, from what I understood?
Correct. The fix is in two parts - one already landed and the other has
an open PR -> https://github.com/canonical/cloud-init/pull/6044
> And what about focal and oracular? Is this
The Problem
The problem is obviously system instability due to memory pressure, but
what can an admin do about it?
Some options exist to configure the priority of processes killed due to
memory pressure.
Non-snap processes can be configured via systemd using OOMScoreAdjust[1]
(kerne
** Description changed:
A logic error in some code I wrote caused lxd to spawn many qemu VMs
which caused memory pressure. This caused the OOM killer to be invoked,
which killed gnome-character. Because the DefaultOOMPolicy is set to
"stop", this caused dbus.service to stop. My system user
Public bug reported:
[ 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).
[ Test Plan ]
Tested via https://github.com/canonical/cl
Public bug reported:
My journal is filling up with logs like this:
Feb 03 19:33:10 arc systemd[8685]: Failed to open /dev/pts device,
ignoring: Inappropriate ioctl for device
There are dozens to hundreds of this exact message per service started.
Many originate from PID 1, others from the user s
Public bug reported:
[ Impact ]
Cloud-init immediately reconfigures the network when 1) hotplug is
enabled and 2) a new device is added. AWS IMDS might not (yet) have the
interface configuration available by the time that the device is visible
to the instance. This means that new interfaces are s
** Changed in: cloud-init
Importance: Unknown => Undecided
** Changed in: cloud-init
Status: Fix Released => New
** Changed in: cloud-init
Remote watch: github.com/canonical/cloud-init/issues #5849 => None
** No longer affects: cloud-init
--
You received this bug notification becaus
> You mention that it was fixed upstream but the bug you reference is
open and has mention of a fix?
Oh you're right. I'm not sure why I said that.
> Also is that an issue with the settings interface or only using
gsettings on the cmdline?
Settings interface, I haven't tried using gsettings on t
I may have a fix for this issue. Please test the code in this PR:
https://github.com/canonical/cloud-init/pull/5913/files
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089185
Title:
Releasing fails
Public bug reported:
Setting org.gnome.desktop.datetime automatic-timezone to true seems to
have no effect. This is because location services is disabled. This is
unintuitive - a toggle should do what it advertises or be blocked when
the system is in a state that will cause the toggle to not work
** Changed in: cloud-init (Ubuntu)
Status: New => Won't Fix
** Changed in: juju (Ubuntu)
Status: New => Won't Fix
** Changed in: cloud-init (Ubuntu)
Status: Won't Fix => Invalid
** Changed in: juju (Ubuntu)
Status: Won't Fix => Invalid
--
You received this bug notif
> While GH-5849 could have the same root cause, at first glance, the
code paths appear to be different.
Agreed.
> until we can get the full logs
A minimal reproducer is also required so that a fix can be developed and
validated.
--
You received this bug notification because you are a member of
This was also reported from Noble and a report was made upstream. I
would link the upstream bug tracker and noble, but this Launchpad
functionality appears currently broken.
[1] https://gitlab.com/apparmor/apparmor/-/issues/445
** Changed in: ubuntu-release-upgrader
Importance: Unknown => Unde
** Bug watch added: gitlab.com/apparmor/apparmor/-/issues #445
https://gitlab.com/apparmor/apparmor/-/issues/445
** Also affects: ubuntu-release-upgrader via
https://gitlab.com/apparmor/apparmor/-/issues/445
Importance: Unknown
Status: Unknown
--
You received this bug notificatio
** Description changed:
A logic error in some code I wrote caused lxd to spawn many qemu VMs
which caused memory pressure. This caused the OOM killer to be invoked,
which killed gnome-character. Because the DefaultOOMPolicy is set to
"stop", this caused dbus.service to stop. My system user
** Description changed:
A logic error in some code I wrote caused lxd to spawn many qemu VMs
which caused memory pressure. This caused the OOM killer to be invoked,
which killed gnome-character. Because the DefaultOOMPolicy is set to
"stop", this caused dbus.service to stop. My system user
** Description changed:
A logic error in some code I wrote caused lxd to spawn many qemu VMs
which caused memory pressure. This caused the OOM killer to be invoked,
which killed gnome-character. Because the DefaultOOMPolicy is set to
"stop", this caused dbus.service to stop. My system user
** Also affects: snapd
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089800
Title:
Ubuntu desktop is unstable under memory pressure due to undesireable
Public bug reported:
A logic error in some code I wrote caused lxd to spawn many qemu VMs
which caused memory pressure. This caused the OOM killer to be invoked,
which killed gnome-character. Because the DefaultOOMPolicy is set to
"stop", this caused dbus.service to stop. My system user slice wasn
** Attachment added: "journalctl_oom.log"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2089800/+attachment/5840840/+files/journalctl_oom.log
** Also affects: systemd
Importance: Undecided
Status: New
** No longer affects: systemd
--
You received this bug notification bec
** Also affects: subiquity
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089393
Title:
package cloud-init 24.3.1-0ubuntu0~24.04.2 failed to install/upgra
Please gather the logs as described in [1] and report back.
Which image did this last succeed in?
I just linked the upstream bug and set the downstream bug to "invalid".
[1] https://docs.cloud-init.io/en/latest/howto/bugs.html#collect-logs
** Bug watch added: github.com/canonical/cloud-init/iss
This doesn't look like a cloud-init bug. Cloud-init is not an
installer[1].
I just added subiquity to this bug report.
[1] https://canonical-subiquity.readthedocs-hosted.com/en/latest/intro-
to-autoinstall.html
** Also affects: subiquity
Importance: Undecided
Status: New
** Changed in
> the most technically advantageous and correct way to configure ssh
Agreed
> How is cloud-init making sure another file in sshd_config.d isn't
superseding its config?
It isn't. I just filed an upstream bug to track this as an issue - and
linked it above.
> sshd -T should be consulted, instead
> Perhaps an acceptable solution could be to write the file only if
cloud-init needs to overwrite the value to "no", but if the value is
"yes", the openssh default, it shouldn't create the file.
This would require cloud-init to implement a parser which correctly
parses all of sshd's configuration
** Changed in: lptools
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/1974061
Title:
Fails on python3.10 (fix linked)
To manage notifications about this
I also hit this issue on Noble, however, I have libtraceevent installed
yet this does not resolve the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2075101
Title:
perf unsupported tracepoint
Looking at this again, I'd like to point out that this bug is invalid
for the following reasons:
1. cloud-init didn't put the README in your boot partition - so you should file
a bug against whatever tool put it there
2. The links that you mentioned do indeed work.
The PR I linked above just upd
** Changed in: cloud-init (Ubuntu)
Status: New => Triaged
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Description changed:
MAAS uses curtin to create a cloud-init configuration using curtin's
debconf_selections. Cloud-init's postinst script generates the p
Thanks for reporting Evan!
Here is the proposed fix https://github.com/canonical/cloud-
init/pull/5741
Please note that Lunar Lobster is EOL, so will not receive future cloud-
init updates.
** Changed in: cloud-init (Ubuntu)
Status: New => In Progress
--
You received this bug notificati
This behavior is expected in ubuntu-minimal, but should not occur in
non-minimal images. This is actually an issue in cloud-init on some
versions of cloud-init. The fix was just committed[1] to upstream and
should be available in the 24.4 release.
[1] https://github.com/canonical/cloud-init/pull/5
** Also affects: linux-kvm (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-kvm (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux-kvm (Ubuntu Oracular)
Importance: Undecided
Status: New
** Package changed: linux-kvm (Ubun
** Description changed:
MAAS uses curtin to create a cloud-init configuration using curtin's
debconf_selections. Cloud-init's postinst script generates the preseed
configuration based on debconf settings.
This design is undesirable for several reasons:
1. this design unnecessarily
Public bug reported:
MAAS uses curtin to create a cloud-init configuration using curtin's
debconf_selections. Cloud-init's postinst script generates the preseed
configuration based on debconf settings.
This design is undesirable for several reasons:
1. this design unnecessarily requires a distro
Agreed, it looks like this is fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1974061
Title:
Fails on python3.10 (fix linked)
To manage notifications about this bug go to:
https://bugs.launchp
> By providing a quirk if cloud-init gets included in an image that doesn't
> already contain cloud-init, we can prevent this pitfall by adding something
> like the following across upgrade.
>
> cat > /etc/cloud/cloud-init.disabled < Disabled by do-release-upgrade because cloud-init was pulled in
Cloud-init now supports event reporting, so closing this item. If you
believe this to be not completed please open a new bug against cloud-
init on Github with more details.
** Changed in: cloud-init (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because
TUN devices do not have a mac address, and therefore this issue has been
resolved[1] since 17.1. Closing
[1] https://github.com/canonical/cloud-
init/commit/ebc9ecbc8a76bdf511a456fb72339a7eb4c20568#diff-64cfbd59f8e1f952e493a0a0198ad52030d7f1809d46e84f1645515045f40270
** Changed in: cloud-init (Ub
The benefit is in kernel boot time, so by the time cloud-init has
started, it will be too late to benefit the first boot. If such a
benefit is even wanted (given the compatibility concerns previously
cited), I suspect that the initial proposal of making this part of image
build would make more sens
Cloud-init now prefers dhcpcd over dhclient, which includes RFC 5227
support. Closing.
** Changed in: cloud-init (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
On 24.04 and later Ubuntu's grub packaging uses
"cloud_style_initialization" and therefore cloud-init isn't required to
select the grub install target anymore.
** Changed in: cloud-init (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of
** 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/1703789
Title:
Disk setup example text only lists MBR as valid table_type
T
** Changed in: cloud-init (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: cloud-init (Ubuntu Focal)
Status: Fix Committed => Fix Released
** Changed in: cloud-init (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification becau
> cloud-init docs are not clear that ';' in kernel cmdline is
potentially missmarsed by bootloaders, and thus the values passed to ds=
should be ideally escaped like ds='all the settings' because \; to
separate key-value pairs can be eaten easily. see the below confusing
where most of the cmdline a
** Changed in: cloud-init (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1675571
Title:
Cloud-init update renders secondary addresses to be incompatible
** 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/1303934
Title:
no error message to console when cloud-config-url fails to lo
The problem that was initially reported was resolved in this bug report.
Cloud-init was behaving as expected so setting to invalid.
** Changed in: cloud-init (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Changed in: cloud-init (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861128
Title:
getty.target starts before cloud-config is done
To manage notific
> [ Chad Smith ]
> * Replace cloud-init.service on NetworkManager images to address an ordering
>cycle interfering with autoinstall with ubuntu-desktop-installer.
>(LP: #2008952)
It sounds like you've correctly diagnosed the root cause.
> Is there something to be fixed on either side?
see the following gnome-shell crash link:
https://errors.ubuntu.com/oops/3aa89b1a-08f5-11ef-9dd2-fa163ec44ecd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064736
Title:
gnome crashes
To manage n
I just discovered
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/2021523.
This bug might be a duplicate of that one, but I'm not sure whether the
dialogue behavior is a gstreamer issue or due to another project
(totem/snapd/etc). For now I'll add gstreamer to this issue and let
someone
Public bug reported:
My attempts to get it to work with gnome video (Totem) fail due to a
missing decoder:
When I start the video with `xdg-open some.mp4`, in a window over the
first frame of the video player I get a popup that says:
```
Unable to play the file
meta/x-gst-fourcc-mett decoder is
I believe that this can be closed. On noble, totem has the following
mimetypes in /usr/share/applications/org.gnome.Totem.desktop
MimeType=application/mxf;application/ram;application/sdp;application/vnd.apple.mpegurl;application/vnd.ms-
asf;application/vnd.ms-wpl;application/vnd.rn-
realmedia;appl
Thanks for reporting this issue! By the changed file it looks like
something (subiquity?) is changing one of cloud-init's service files.
Since it looks like this is an issue in an external project, I'm setting
this issue to Invalid on the cloud-init project for now.
** Changed in: cloud-init (Ubu
I haven't tested the diff, but this looks like an improvement to me. The
new output message improves the messaging to the user with a clue that
LABEL resolution is involved in fs type lookup and a possible source of
the issue.
+1 thanks @bdrung
--
You received this bug notification because you a
After digging in a little bit I noticed that this is just a case of a
confusing error message. It turns out that the label was just missing
from this filesystem. I'll update the bug title accordingly.
** Summary changed:
- initramfs-tools can't identify root filesystem type
+ initramfs-tools rep
Public bug reported:
When I attempt to regenerate an initramfs for a new root filsystem,
update-initramfs is unable to identify the filesystem type of this
initramfs.
```
# update-initramfs -u
update-initramfs: Generating /boot/initrd.img-5.15.0-1059-kvm
W: Couldn't identify type of root file sys
This is a duplicate of https://bugs.launchpad.net/ubuntu/+source/gnome-
shell-extension-tiling-assistant/+bug/2063970
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065869
Title:
Noble tiling overla
> The desktop crashes after some time and a hard reboot is needed (going
so far to unplug and re-plug).
This happens while trying to upgrade cloud-init I assume? Does this
reproduce for you? I just tried upgraded cloud-init from 23.3.1-0ubuntu2
to 24.1.3-0ubuntu1~23.10.2 without error. The journal
** Attachment added: "added screenshot"
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/2066027/+attachment/5779381/+files/Screenshot%20from%202024-05-17%2010-33-25.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Public bug reported:
Firefox is currently eating 100% CPU (firefox was nearly unusable,
confirmed with htop), however the gnome system monitor reports 0.99%.
This does not appear to be a simple multiplication error since a single
process called Isolated Web Co is reported as much higher at 6.31
p
Public bug reported:
Sometimes when dragging a window on Gnome to an edge to arrange window
tiling, the translucent orange overlay will cover the top half of the
screen. This has been happening on Noble for a month or two now. Usually
just resizing the tiled window will make this overlay disappear
Will do once I return.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064736
Title:
gnome crashes
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell
Is this behavior supposed to be fixed in 24.04? I see a similar report
here[1] based on 24.04 where the apparent fix involves removing
optional: true to avoid blocking boot.
[1] https://github.com/Joshua-Riek/ubuntu-rockchip/issues/757
** Bug watch added: github.com/Joshua-Riek/ubuntu-rockchip/is
Public bug reported:
second time that gnome crashed in two days while moving windows around
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gdm3 46.0-2ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
NonfreeKernelModules: zfs
ApportVersion:
Public bug reported:
graphics crashes, requires reboot
this has happened a few times recently - typically during periods of
activity but not always.
See the journal log from the last boot below:
Apr 30 21:07:15 arc kernel: snd_hda_intel :1f:00.1: Unable to change power
state from D3hot to
Public bug reported:
Originally reported on Github[1], cloud-init released a change in the
cli[2] that broke former cloud-init cli commands.
Previously `cloud-init -f init` was allowed, but after the 24.1 SRU
release to Jammy, this broke and
now the following invocation is required to accompli
This was resolved in upstream cloud-init in 23.3, which moved
Before=systemd-user-sessions.service from cloud-init.service to cloud-
config.service to resolve LP: #2013403. That change was temporarily
reverted on Ubuntu due to a snap-related performance regression. On
Noble and newer, the snap regr
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2039505
Title:
Time To SSH Regression
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2039505/+s
Public bug reported:
When trying to log in from locked / sleeping desktop, gnome crashed.
I have three monitors connected via displayport to this card.
dmesg snip:
[Thu Apr 11 08:12:57 2024] audit: type=1107 audit(1712844779.171:174815):
pid=1799 uid=103 auid=4294967295 ses=4294967295 subj=unc
Public bug reported:
I connected the system to wifi using gnome's settings.
Stuck at the "Preparing Ubuntu..." screen burning 100% cpu on one core.
The process burning CPU (currently at 27m runtime) is:
python3 -m subiquity.cmd.server --use-os-prober --storage-version=2
--postinst-hooks-dir=/sn
** Attachment added: "strace.40801"
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2060326/+attachment/5761743/+files/strace.40801
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Public bug reported:
For the last hour or so, unattended upgrades has been stuck burning 100%
of a cpu.
series: noble
version: 2.9.1+nmu4ubuntu1
** Affects: unattended-upgrades (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a memb
** Also affects: cloud-utils (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: github.com/canonical/cloud-utils/issues #46
https://github.com/canonical/cloud-utils/issues/46
** Also affects: cloud-utils via
https://github.com/canonical/cloud-utils/issues/46
Importa
Just to recap some thoughts from the conversation cloud-init devs just
had:
- Automatically killing non-interactive processes may have far-reaching
changes. It may leave many packages besides cloud-init exposed. Any service
that calls `apt upgrade` etc non-interactively may get killed. How confi
> If you can add your details for your "specific" FW13 AMD to the upstream bug
> maybe others who are affected can help with building the pattern.
> I mean the memory vendor, speed of memory, amount, channel configuration.
this system has a single DIMM which was provided by framework: DDR5-5600
-
After setting UMA_Game_Optimized, I can confirm that (after 30 minutes
of usage), the system appears far more stable. Since X11 appeared stable
I also switched back to Wayland which was previously unusable and this
also appears to be working.
I'll also report back once I am able to test the new ke
>> Should this fix the flickering issue? I'm happy to test it out.
>
> It will fix a colored flickering;
My flickering has mostly actually usually been white - not colored (though
I was seeing the colored flickering lots before I switched off of Wayland,
which crashed too often with multiple monit
Thanks for the update @superm1, I appreciate the help.
> I suggest updating to 6.8.0-20 though, this 6.8.0-11 has an old 6.8-RC
snapshot and there are other bugs that got fixed later on in the
6.8-RC's.
Should this fix the flickering issue? I'm happy to test it out.
> FYI - there are two workaro
> due to network not being fully set up when startup scripts are run.
google-startup-scripts.service starts well after the network is online,
so I think that the actual reason is that cc_apt_configure hasn't ran
yet when the startup script starts. The diff looks like some apt mirrors
configured by
** 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:
-
- added support for WSL (Windows Subsystem for Linu
** Changed in: cloud-init (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056439
Title:
Latest cloud-init fails with AttributeError: 'DataSourceVM
Since returning this behavior to previous state on jammy and focal would
revert this bug fix and other bugfixes, the change in behavior is both
minor and seen as a bugfix, and it is not expected that many users are
making use of this old behavior (it took almost a year to see a report
since the cha
solution worked for me as well
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056562
Title:
package shim-signed 1.57+15.8-0ubuntu1 failed to install/upgrade:
subproces van pakket shim-signed werd
Public bug reported:
an interesting amdgpu issue:
I currently have two external monitors, and only one will display the
desktop at a time - the other is completely white. The interesting thing
is that with each interrupt that the kernel receives from keyboard /
mouse, the screens will flip which
I am setting the importance to low for the following reasons:
- reverting the change would reintroduce a different bug[1]
- a workaround has been provided
- the change in behavior is minor
- the change was introduced almost a year ago without any reports yet
[1] https://bugs.launchpad.net/cloud-i
Public bug reported:
Originally filed on Github[1]
In 612b4de (23.2) cloud-init switched the ds= kernel key from optionally
matching on nocloud-net to forcibly selecting nocloud-net.
This means that anyone that previously had a matching `ds=nocloud*` in
their kernel commandline that _did not_ wa
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:
- added support for WSL (Windows Subsystem for Linux)
- support for dh
Subject: Fixed in cloud-init version 22.2.
Comment: This bug is believed to be fixed in cloud-init in version 22.2. If
this is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init (Ubuntu)
Status: Fix Committed => Fix Released
This bug is believed to be fixed in cloud-init in version 22.2. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a membe
I agree with falcojr and dbungert's analysis (#6 and #8, respectively)
on cloud-init's role in this issue; this looks like a symptom that gets
reported via cloud-init not an issue caused by it.
** Changed in: cloud-init (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notif
** Changed in: cloud-init (Ubuntu)
Status: In Progress => 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/1961446
Title:
sru cloud-init (22.1 update) Bionic, Focal, Impish
To mana
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal verification-needed-impish
** Tags added: verification-done verification-done-bionic
verification-done-focal verification-done-impish
--
You received this bug notification because you are a member of Ubunt
The attached tarball include passing integration tests for gce, lxd
container, lxd vm, for bionic, focal, and impish. The curtin cloud-init
integration tests are also included.
Impish on gce had a transient failure. The following rerun succeeded.
** Attachment added: "curtin-gce-lxd.tar.gz"
h
** Description changed:
[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:
- - sources/azure: report ready in local phase [Chris Patterson]
- - sources/azur
** Description changed:
[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:
-
- - sources/azure: report ready in local phase (#1265) [Chris Patterson]
- - s
** Description changed:
[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:
-*
-
- See the changelog entry below for a full list of changes and bugs.
-
1 - 100 of 106 matches
Mail list logo
