** Changed in: oem-priority
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081124
Title:
systemd service dependency loop between cloud-init, NetworkManager and
dbu
thank you Mauricio for the detailed review!
>>It looks like most tests in the requested test_hotplug.py are SKIPPED
>>(summary below), so I just wanted to confirm:
>> 1) Is that is expected? And
Yes, this skipping is expected on all platforms except for Noble and Ec2
which have a bit more detai
updated test-case-1 desktop logs showing all formerly affected systemd
sevices are healthy on first boot
** Attachment added: "test-case-1-desktop-ordering-cycle.log"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2081124/+attachment/5823530/+files/test-case-1-desktop-ordering-cycle
OEM team would like to expedite SRU aging on this bug now that it is
verified because the affected offerings for noble use daily image
builds. So, the sooner this fix releases the sooner builds are
unblocked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
test-case-1: confirm ordering cycle issues on daily Noble desktop,
confirm fix with noble-propose cloud-init
** Attachment added: "test-case-1-desktop-ordering-cycle.log"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2081124/+attachment/5823529/+files/test-case-1-desktop-ordering-c
Thank you Andreas.
Attached are the logs for all testcases in test case 2. The TLDR is happy
hotplug tests on ec2, azure, gce and a solid performance improvement in
bootspeed.log time measurements (across 3 samples):
- Avg time to ssh:`1.12 seconds faster
- Avg time to spent in systemd on
** Description changed:
[ Impact ]
cloud-init 24.2 shifted the systemd configuration of cloud-init-
hotplugd.socket to earlier in boot before sysinit.target, but still
retained the systemd unit DefaultDependencies. This lead to a systemd
ordering cycle which affects only Ubuntu Live D
** Description changed:
[ Impact ]
cloud-init 24.2 shifted the systemd configuration of cloud-init-
hotplugd.socket to earlier in boot before sysinit.target, but still
retained the systemd unit DefaultDependencies. This lead to a systemd
ordering cycle which affects only Ubuntu Live D
** Description changed:
[ Impact ]
cloud-init 24.2 shifted the systemd configuration of cloud-init-
hotplugd.socket to earlier in boot before sysinit.target, but still
retained the systemd unit DefaultDependencies. This lead to a systemd
ordering cycle which affects only Ubuntu Live D
Note that https://bugs.launchpad.net/ubuntu/+source/cloud-
init/+bug/2079224 just cleared SRU. So, this bug should be able to
progress for review into noble-proposed for verification.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
** Tags removed: verification-needed verification-needed-focal
verification-needed-jammy verification-needed-noble
** Tags added: verification-done verification-done-focal
verification-done-jammy verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Bu
** Description changed:
- We got errors that some services like snapd and NetworkManager is not
- started when running cloud-init or desktop, excerpt from journal below:
+ [ Impact ]
+
+ cloud-init 24.2 shifted the systemd configuration of cloud-init-
+ hotplugd.socket to earlier in boot before s
supplemental successful retries and known upstream bug on lxd_vm focal
** Attachment added: "lxd_vm-focal-retries.log"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2079224/+attachment/5821235/+files/lxd_vm-focal-retries.log
--
You received this bug notification because you are a
Note that this upload for Noble is queued
https://launchpad.net/ubuntu/noble/+queue?queue_state=1&queue_text=cloud-init
and sitting behind the active SRU 24.3.1 to Noble.
The SRU process bug https://bugs.launchpad.net/bugs/2079224 is just awaiting
partner verification feedback on that SRU to pub
Curtin SRU logs success
** Attachment added: "sru-curtin-24.1.3.log"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2079224/+attachment/5820909/+files/sru-curtin-24.1.3.log
** Description changed:
== Begin SRU Template ==
[Impact]
This release sports both bug-fixes and new f
SRU successful verification logs and test retries for EC2, GCE, Azure,
lxd_vm, lxd_container on Focal, Jammy and Noble.
** Attachment added: "sru-24.3.1.tar"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2079224/+attachment/582/+files/sru-24.3.1.tar
** Description changed:
** 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/2081124
Title:
systemd service dependency loop between cloud-init, Networ
This particular bug is not applicable for livecd-rootfs, as this is a
cloud-init systemd ordering issue.
There is a separate livecd-rootfs bug and fix for Oracular only
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2081325 which is
already queued for oracular-proposed
--
You rec
Fix uploaded to Ubuntu Oracular as 24.4~3+really24.3.1-0ubuntu4
(blocked per Beta freeze)
https://launchpad.net/ubuntu/oracular/+queue?queue_state=1&queue_text=cloud-
init
Fix uploaded as well to the unapproved queue for SRU as version
24.3.1-0ubuntu0~24.04.2 it is queued behind current SRU of
Thanks Alberto!
Upstream cloud-init fix landed per
https://github.com/canonical/cloud-init/pull/5722.
Related to this bug is an Oracular Desktop livecd-rootfs update which is
needed due to cloud-init.service being renamed to cloud-init-
network.service.
https://bugs.launchpad.net/ubuntu/+source/
** Changed in: livecd-rootfs (Ubuntu Oracular)
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/2081325
Title:
Oracular: systemd override file not applied du
Marking cloud-init task as won't fix as this is something needed in
livecd-rootfs overrides/dropins.
** Changed in: cloud-init (Ubuntu Oracular)
Status: New => In Progress
** Changed in: cloud-init (Ubuntu Oracular)
Assignee: (unassigned) => Chad Smith (chad.smith)
**
Tagging this rls-oo-incoming as this ordering issue affects Oracular
Desktop images as well.
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Critical
** Tags added: rls-oo-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
ecd-rootfs (Ubuntu Oracular)
Importance: Critical
Assignee: Chad Smith (chad.smith)
Status: Confirmed
** Also affects: cloud-init (Ubuntu Oracular)
Importance: Critical
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
ntu)
Importance: Critical
Assignee: Chad Smith (chad.smith)
Status: Confirmed
** Tags: rls-oo-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081325
Title:
Oracular: syste
The differences we are seeing between a working Desktop ubuntu image
with /var/log/installer/media-info 202408271 are that cloud-init
published 24.2 via SRU to the newer Noble image
In that SRU was a shift to when cloud-init-hotplugd.socket and cloud-
init-hotplugd.service units are ordered[1]
T
ok I'm able to reproduce the ordering cycle in ephemeral boot stage for
cloud-init-hotplug.service on noble images dated 20240916
cloud-init-hotplugd.service/socket may be the symptom tying into this
ordering issue too. Digging a bit more today as they may be a symptom of
the same problem and syst
I have also confirmed that livecd-rootfs doesn't appear to have changed
their "drop-in" of cloud-init.service files
https://git.launchpad.net/ubuntu/+source/livecd-rootfs/tree/live-
build/functions#n1060 so it's unlikely a new cloud-init issue introduced
across an SRU boundary.
This makes me think
From the SOS report issue presents on image with this build-info with
whatever additional OEM config is presented as autoinstall-user-data
Ubuntu OEM 24.04.1 LTS "Noble Numbat" - Release amd64 (20240911)
I'm trying to download latest Ubuntu Desktop noble to reproduce this problem
from live Desk
Thank your for filing this bug, if possible, please perform the
following to aid in debugging:
1. inform the bug on which Ubuntu release this issue occurs, possibly
the desktop image build date,
2. # get versions of network-manager, systemd and cloud-init
for pkg in cloud-init systemd network-man
** Changed in: cloud-init (Ubuntu Bionic)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067660
Title:
deprecate ubuntu_advantage config key from user-data in favor
** Tags added: rls-oo-incoming
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) => Chad Smith (chad.smith)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080688
Title:
oracu
Upstream pull request landed https://github.com/canonical/cloud-
init/pull/5701
** 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
Public bug reported:
Affects cloud-init version:
24.4~3+really24.3.1-0ubuntu1 and
24.4~3+really24.3.1-0ubuntu2
A new feature added in Oracular was to allow NoCloudNet configuration to be
detected by providing system configuration in /etc/cloud/cloud.cfg.d/*.cfg like
the following:
datasource
@racb this was missing SRU documentation as far as the previous bionic
upload was concerned as we thought originally this upload may be taken
direct into esm-infra pockets.
But, because this supplemental cloud-config user-data key is required at
initial instance launch in non-pro images, providi
** Description changed:
[ Impact ]
- * This backport supplements cloud-config user-data schema to allow
+ * This backport supplements cloud-config user-data schema to allow
customers to provide an `ubuntu_pro:` key in cloud-config user-data to
auto-attach non-pro images to Ubuntu Pro at
** Description changed:
+ [ Impact ]
+
+ * This backport supplements cloud-config user-data schema to allow
+ customers to provide an `ubuntu_pro:` key in cloud-config user-data to
+ auto-attach non-pro images to Ubuntu Pro at instance launch. This
+ ubuntu_pro key support is provided in additi
** 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:
- - Add AOSC linux distribution support (#5310)
- -
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:
- Add AOSC linux distribution support (#5310)
- Add OpenEuler suppo
** Changed in: cloud-init (Ubuntu)
Status: New => 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/2071762
Title:
sru cloud-init (24.2 update) to focal, jammy and noble
To manage n
Confirmed the URU 1:24.04.21 disables cloud-init across upgrade via
marker file. Marking invalid for cloud-init as running on first boot is
cloud-init default mode of operation.
** Changed in: cloud-init (Ubuntu)
Status: New => Invalid
** Changed in: cloud-init (Ubuntu Noble)
Status
The blocking release of python3-defaults just published to noble and
jammy yesterday per bug
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2075337.
We should be able to proceed with release of cloud-init as all
verification was done as of 08-01-2024
** Tags removed: verification-
Adapted script to support installing sqt-launcher from universe in
jammy.
** Attachment added: "sru-2075337.sh"
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2075337/+attachment/5808150/+files/sru-2075337.sh
--
You received this bug notification because you are a member of
Verification logs success noble.
csmith@midtown:~$ ./sru-2075337.sh
+ cat
+ SET_LOCALE_YAML='#cloud-config
password: passw0rd
chpasswd: { expire: False }
ssh_pwauth: True
locale: fr_FR
'
+ export LANG=en_AU.ISO-8859-1
+ LANG=en_AU.ISO-8859-1
+ for RELEASE in noble
+ NAME=sru-2075337-noble
+ lxc la
Verification script for noble
- verify current failure with existing python3-defaults and cloud-init reinstall
- verify success with python3-defaults from -proposed and cloud-init reinstall
** Attachment added: "sru-2075337.sh"
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2
Since cloud-init is blocking our releases on this bug. I'll take this
test plan and tag when finished
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2075337
Title:
[SRU] py3clean fails when using alt
I can confirm in Ubuntu cloudimages on LXD that do-release-upgrade
across Jammy -> Noble succeeds having run cloud-init on first image
launch in Jammy, removing the cache due to python3 version upgrade, and
redetecting LXD datasource config on reboot into Noble with proper
instance-id detection.
I
> 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.
Ahh the cleared cache is what triggers cloud-init to re-run thereby
reapplying any user-data it detects on that subsequent boot. Since
default system configur
In the logs there we can see that cloud-init across reboot added a
WARNING because it was unable to redetect the LXD datasource in noble:
2024-08-08 18:55:53,280 - cc_final_message.py[WARNING]: Used fallback
datasource
This discovery of a new datasource triggers cloud-init to re-run on a system
Can we upload cloud-init collect-logs to this bug to see cloud-init's
behavior across this reboot? If cloud-init thinks it didn't run for
some reason across upgrade then it may re-run thinking it is a fresh
install. Having visiblity to the full /var/log/cloud-init.log would be
helpful here.
--
Y
1. Confirmed diff from packaged cloud-init.service and override
root@lcd-o:~# diff -urN /lib/systemd/system/cloud-init.service
/etc/systemd/system/cloud-init.service
--- /lib/systemd/system/cloud-init.service 2024-06-26 18:30:42.0
+
+++ /etc/systemd/system/cloud-init.service
Thanks @alberto. I confirmed the following:
The question of whether apt upgrade would show us the Files changed prompt
which would break unattended upgrades. The answer is we don't have to worry
about it because apt upgrade only reacts to changes in files registered by the
deb package as conff
@andreas thank you for the review here.
We resolved my cut-n-paste issues in debian/changelog and have redacted
the duplicated entries pulled up from a prior debian/changelog section.
The superfluous d/p/chad was due to snap-shotting from a local
development branch instead of our public downstrea
@Dan Bungert. Since this was my changeset, I thought I'd put up a PR as food
for thought which uses the override that Brett mentioned. It avoids the
wholesale replacement of the entire unit file and just addresses Before and
After config in the supplemental override file.
I also updated the Af
** 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:
- feat: Add support for FTP and FTP over TLS (#4834)
** 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:
- feat: Add support for FTP and FTP over TLS (#4834)
** 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:
- feat: Add support for FTP and FTP over TLS (#4834)
Not targeting Mantic for release due to expected EOL 2024-07-11 not
leaving enough time to SRU verify this release.
** 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 h
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:
* : Create list with LP: # included>
See the changelog entry below
** Summary changed:
- netplan apply triggers udev add events for every network interfdace
+ netplan apply triggers udev add events for every network interface
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
** Description changed:
[ Impact ]
Cloud-init recently added policy-based routing for netplan-only systems
on EC2. In order to gate the netplan-specific code, it checked to see in
the netplan activator was being used. However, if the datasource is
fetched in init-local timeframe (such
This bug was fixed in the package cloud-init - 24.2~4g5f40426f-0ubuntu1
---
cloud-init (24.2~4g5f40426f-0ubuntu1) oracular; urgency=medium
* Upstream snapshot based on upstream/main at 5f40426f.
- Bugs fixed in this snapshot: (LP: #2066985)
The fix for this bug in the pre
** Description changed:
[ Impact ]
Cloud-init recently added policy-based routing for netplan-only systems
on EC2. In order to gate the netplan-specific code, it checked to see in
the netplan activator was being used. However, if the datasource is
fetched in init-local timeframe (such
Setting this task back to new for oracular as the fix provided in
https://github.com/canonical/cloud-init/pull/5321 ended up breaking
policy-based routing rendering for the netplan-based renderers on multi-
nic instance types on Ec2.
Upstream fix https://github.com/canonical/cloud-init/pull/5361 r
Public bug reported:
In upstream cloud-init ubuntu_advantage user-data cloud-config key is
deprecated in favor of ubuntu_pro to better align with current Ubuntu
Pro product naming and to avoid confusion in howtos, tutorials or
tooling when interacting with Ubuntu Pro offerings.
In an effort to st
** Summary changed:
- Mutli-nic ENI rendering fails if ENI activator not used
+ EC2 multi-nic ENI rendering fails if ENI activator not used
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066985
Title
** Summary changed:
- cloud-init network fails in ipv6-only subnet with multi-NICs
+ EC2: cloud-init network fails in ipv6-only subnet with multi-NICs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/206
sru validation complete noble
csmith@downtown:~$ bash ./sru-2064132.sh
+ cat
+ cat
+ for SERIES in "noble"
+ echo '-- SRU verification: noble'
-- SRU verification: noble
+ name=test-no-snap-noble
+ lxc launch ubuntu-daily:noble test-no-snap-noble
Creating test-no-snap-nob
=== SRU verification complete jammy ===
csmith@downtown:~$ bash ./sru-2064132.sh
+ cat
+ cat
+ for SERIES in "jammy"
+ echo '-- SRU verification: jammy'
-- SRU verification: jammy
+ name=test-no-snap-jammy
+ lxc launch ubuntu-daily:jammy test-no-snap-jammy
Creating test-no-snap-ja
focal SRU verification complete ===
echo '-- SRU verification: focal'
-- SRU verification: focal
+ name=test-no-snap-focal
+ lxc launch ubuntu-daily:focal test-no-snap-focal
Creating test-no-snap-focal
Starting test-no-snap-focal
+ sleep 6
+ lxc exec test-no-snap-focal -- clou
# verification complete mantic #
csmith@midtown:~$ lxc launch ubuntu-daily:mantic test-m
Creating test-m
Starting test-m file push myfile.yaml
csmith@midtown:~$ lxc file push myfile.yaml test-m/
csmith@midtown:~$ lxc file push setup_proposed.sh test-m/
csmit
test verification complete jammy
csmith@midtown:~$ lxc launch ubuntu-daily:jammy test-jammy
Creating test-jammy
Starting test-jammy
csmith@midtown:~$ lxc file push myfile.yaml test-jammy/
csmith@midtown:~$ lxc file push setup_proposed.sh test-jammy/
csmith@mi
Thanks Timo!
focal verification complete =
csmith@midtown:~$ lxc launch ubuntu-daily:focal test-focal
Creating test-focal
Starting test-focal
csmith@midtown:~$ lxc exec test-focal bash
root@test-focal:~# hostname # confirm test-focal from standard meta-data
test-focal
root@test-focal:~#
This fix is also uploaded for SRU to noble in cloud-init version
24.1.3-0ubuntu3.2
** Tags removed: verification-needed-focal verification-needed-jammy
verification-needed-mantic verification-needed-noble
** Tags added: verification-failed-focal verification-failed-jammy
verification-failed-mant
** Tags added: regression-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064132
Title:
images without snapd installed error on `upgrade_packages: true` user-
data
To manage notifications
Upload to oracular 24.2~2g51c6569f-0ubuntu1 released upstream commit
51c6569f96bee4f91aad5db58765c7abab7ffcdf which resolves this issue.
Uploads are in the unapproved queue which resolve the SRU verification failures
discovered in comment #13:
- mantic: 24.1.3-0ubuntu1~23.10.5
- jammy: 24.1.3-0ub
mantic verification complete
csmith@midtown:~$ lxc launch ubuntu-daily:mantic test-mantic
Creating test-mantic
Starting test-mantic
csmith@midtown:~$ lxc file push myfile.yaml test-mantic/
csmith@midtown:~$ lxc file push setup_proposed.sh test-mantic/
csmith@midtown:~$ lxc exec test-manti
= jammy verification complete
csmith@midtown:~$ lxc launch ubuntu-daily:jammy test-jammy
Creating test-jammy
Starting test-jammy
csmith@midtown:~$ lxc file push myfile.yaml test-jammy/
csmith@midtown:~$ lxc file push setup_proposed.sh test-jammy/
csmith@midtown:~$ lxc exec test-jammy bash
focal verification complete
csmith@midtown:~$ lxc file push myfile.yaml test-focal/
csmith@midtown:~$ lxc exec test-focal bash
root@test-focal:~# # confirm usage failure
root@test-focal:~# cloud-init -f /myfile.yaml init
usage: /usr/bin/cloud-init [-h] [--version] [--debug] [--force]
SRU verification determined that the fix in -proposed was not complete
enough to fix the package_ugprade: true case.
Upstream commit has landed fixing this
issue:https://github.com/canonical/cloud-
init/commit/51c6569f96bee4f91aad5db58765c7abab7ffcdf
Uploads will be pushed to focal/jammy/mantic-p
Sru validation script
** Attachment removed: "sru-2064132.sh"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2064132/+attachment/5774506/+files/sru-2064132.sh
** Attachment added: "sru-2064132.sh"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2064132/+attachment/577
** Summary changed:
- images without snapd installed error on `update_packages: true` user-data
+ images without snapd installed error on `upgrade_packages: true` user-data
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
** Description changed:
[ Impact ]
* SRU of cloud-init 24.1.3 to Focal, Jammy and Mantic introduced a
regression where cloud-init will attempt to call `snap refresh` on new
Ubuntu instance launches if the Ubuntu image does not contain snapd deb
package and optional #cloud-config user
** Description changed:
[ Impact ]
* SRU of cloud-init 24.1.3 to Focal, Jammy and Mantic introduced a
regression where cloud-init will attempt to call `snap refresh` on new
Ubuntu instance launches if the Ubuntu image does not contain snapd deb
package and optional #cloud-config user
** Summary changed:
- cli behavior changed
+ cli behavior changed for commands passing optional --file argument to
cloud-init init, modules or single subcommand
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
** Description changed:
- Originally reported on Github[1], cloud-init released a change in the
- cli[2] that broke former cloud-init cli commands.
+ [ Impact ]
- Previously `cloud-init -f init` was allowed, but after the 24.1 SRU
release to Jammy, this broke and
+ * Environments or scripts
** Also affects: cloud-init (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubunt
Given that all Canonical Ubuntu images (including server minimal and
cloud minimal images) contain snapd deb package, this is not a critical
path concern for Canonical stable supported Ubuntu images. So,
`regression-update` tag is dropped for our specific support paths as
this doesn't regress image
** Description changed:
- In Ubuntu images that do not have snapd debian package installed
- launching with the following user-data triggers cloud-init to run `snap
- refresh` when that command doesn't exist.
+ [ Impact ]
+ * SRU of cloud-init 24.1.3 to Focal, Jammy and Mantic introduced a
+ r
Upstream commit merged https://github.com/canonical/cloud-
init/commit/a6f7577d582aa51d51ca129fcff65313e210d47b
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Committed
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) => Chad Smith (chad.smith)
--
You receive
Upstream github issue re-opened representing this fix:
https://github.com/canonical/cloud-init/issues/5143
upstream Pull request fixing this issue:
https://github.com/canonical/cloud-init/pull/5224
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Public bug reported:
In Ubuntu images that do not have snapd debian package installed
launching with the following user-data triggers cloud-init to run `snap
refresh` when that command doesn't exist.
reproducer:
lxc launch ubuntu-daily:jammy test-no-snap
sleep 3
lxc exec test-no-snap -- cloud-in
Just because tags show verification needed. I ran through and validated
the netplan on jammy has right limited perms as root-rw and no warnings
emitted by netplan apply due to permissions
## test logs
csmith@midtown:~$ lxc launch ubuntu-daily:jammy t-j
Creating t-j
Starting t-j
csmith@midtown:~$
** Changed in: cloud-init (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059337
Title:
noble: needrestart triggering SIGTERM of cloud-final.service
pre
Thanks Lukas: +1 on this changeset not degrading early boot install
scenarios where systemd services are ordered After=systemd-networkd-
wait-online.service
Preliminary testing on Azure platform look good with accelerated networking
enabled have confirmed dual-nic tests correctly configure the p
Marking won't fix as the resolution was in needrestart not cloud-init
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059337
Title:
noble: needrestart triggering SIGTERM of cloud-final.service
prev
Closing cloud-init task for this bug as cloudimages created after
20240408 contain appropriate needrestart to defer cloud-final.service
during cloud-init package upgrade.
** Changed in: cloud-init (Ubuntu Noble)
Status: Confirmed => Won't Fix
--
You received this bug notification because
For the cloud-init element/task of this bug, before we change our
current upstream grub_dpkg debconf set-selections behavior for boot
device detection, we need to consider the following scenarios where the
absence of cloud-init grub_dpkg behavior may be insufficient.
If Ubuntu primary use-cases de
Thanks Dan, on a patch for subiquity placing an /etc/cloud/cloud.cfg.d/
snippet into the target installed system. This approach will still allow
for live server/desktop install path where customers which require
cloud-init's default grub_dpkg behavior for some corner case could still
turn that beha
@Mate thanks for the patch suggestion and triage work here.
While this approach will work for live-server/live-desktop and or Ubuntu
cloudimage which have downstream grub2 deb fixes for handling the 'new'
grub-pc/cloud_style_intialization debconf setting, are we missing other
use-cases that will f
1 - 100 of 976 matches
Mail list logo
