images without snapd installed error on `upgrade_packages: true` user-data

Bug #2064132 reported by Chad Smith
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init (Ubuntu)
Status tracked in Oracular
Focal
Fix Committed
Undecided
Unassigned
Jammy
Fix Committed
Undecided
Unassigned
Mantic
Fix Committed
Undecided
Unassigned
Noble
Fix Committed
Undecided
Unassigned
Oracular
Fix Released
Critical
Chad Smith

Bug Description

[ 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-data is provided which contains `upgrade_packages: true`.

 * Such optional user-data on custom ubuntu images will result in cloud-init exiting in error condition as seen from cloud-init status due to the following error message:
 - ('package_update_upgrade_install', ProcessExecutionError("Unexpected error while running command.\nCommand: ['snap', 'refresh']\nExit code: -\nReason: [Errno 2] No such file or directory: b'snap'\nStdout: -\nStderr: -"))

This only affects new custom Ubuntu image launches where both of the following conditions are met:
1. image is a custom ubuntu image which does not contain snapd deb package
2. At instance launch, optional #cloud-config user-data contains `package_upgrade: true`

Ubuntu cloudimages published by Canonical for Focal, Jammy and Mantic all currently have the snapd deb package installed.

Even for custom Ubuntu images without snapd deb package installed, this issue is only triggered when #cloud-config contains the optional `package_upgrade: true` during instance launch.

This error log does cause cloud-init status to exit non-zero, but it doesn't affect the integrity of the configuration applied to the system. It is just an undesirable error log message for an unsupported (snap) package manager within the environment.

[ Test Plan ]
 * # launch ubuntu cloud images in LXC, remove snapd, provide "#cloud-config\npackage_upgrade:true" as user-data and clean reboot to force cloud-init to attempt to upgrade any package managers (snap and apt) where applicable.

 * confirm no snap command present in image
 * check cloud-init status --format=yaml to ensure no errors
 * grep snap.*refresh /var/log/cloud-init.log to assert no stray snap refresh is attempted on an image without snap

#!/bin/bash
set -ex
SERIES=$1

cat > pkg-update.yaml <<EOF
#cloud-config
package_upgrade: true
EOF
cat > setup_proposed.sh <<EOF
#/bin/bash
mirror=http://archive.ubuntu.com/ubuntu
echo deb \$mirror \$(lsb_release -sc)-proposed main | tee /etc/apt/sources.list.d/proposed.list
apt-get update -q
apt-get install -qy cloud-init
EOF

for SERIES in "focal" "jammy" "mantic"; do
echo "---------- SRU verification: $SERIES"
name=test-no-snap-$SERIES
if [ "$SERIES" = "focal" ]; then
  LXC_CFG_KEY="user.user-data"
else
  LXC_CFG_KEY="cloud-config.user-data"
fi
lxc launch ubuntu-daily:$SERIES $name -c $LXC_CFG_KEY="$(cat pkg-update.yaml)"
sleep 3
lxc exec $name -- cloud-init status --wait
# assert snap refresh is called on system with snapd
lxc exec $name -- egrep 'snap.*refresh' /var/log/cloud-init.log && echo "SUCCESS: found snap refresh on system with snapd" || echo "FAILED: did not file snap refresh on system with snapd"

lxc exec $name -- apt remove snapd -y
lxc exec $name -- cloud-init clean --logs --reboot
sleep 3

# expect no warnings/errors
lxc exec $name -- cloud-init status --wait --format=yaml || echo "FAILED: errors or warning found"

# ensure no calls to snap refresh
lxc exec $name -- egrep 'snap.*refresh' /var/log/cloud-init.log || echo "SUCCESS: no snap refresh on system without snapd" && echo "FAILED: found snap refresh on system without snapd"

done

[ Where problems could occur ]

The bug above is an unwanted error log that results in cloud-init reporting an error state and non-zero exit code. The error log doesn't erode the actual final configuration applied to the machine, it just sets a state we don't wont to see as cloud-init shouldn't be trying and failing to run snap command if it doesn't exist in the environment. Given that this fix is only performing a subp.which("snap") to assert that the snap command exists in the path before attempting to run "snap refresh" regression potential is negligible. In the unlikely event that the code paths added do fail here, the regression impact woud only result in a slightly different error log that also doesn't impact the overall config applied to the instance at launch.

[ Other Info ]

==== original description ====
In Ubuntu images that do not have snapd deb 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-init status --wait
lxc exec test-no-snap -- apt remove snapd -y

cat > pkg-update.yaml <<EOF
#cloud-config
package_update: true
EOF

lxc config set test-no-snap cloud-init.user-data="$(cat pkg-update.yaml)"
lxc exec test-no-snap -- cloud-init clean --logs --reboot
sleep 3

# expect no warnings/errors
lxc exec test-no-snap -- cloud-init status --wait --format=yaml

# ensure no calls to snap refresh
lxc exec test-no-snap -- egrep 'snap.*refresh' /var/log/cloud-init.logb

Revision history for this message
Chad Smith (chad.smith) wrote :

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

Revision history for this message
Chad Smith (chad.smith) wrote :
Changed in cloud-init (Ubuntu):
status: New → Fix Committed
assignee: nobody → Chad Smith (chad.smith)
Chad Smith (chad.smith)
description: updated
description: updated
Revision history for this message
Chad Smith (chad.smith) wrote (last edit ):

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 streams we claim to support. This SRU remains queued in unapproved queue for Focal, Jammy, Mantic and Novble with priority for next SRU reviewer when time is available as we do want this fixed shortly to better support any derivative Ubuntu images which may have dropped snapd from their images in an effect to shrink that image size even further.

tags: removed: regression-update
Revision history for this message
Andreas Hasenack (ahasenack) wrote :

Reopening the main devel (oracular) task as the fix is not there yet, nor uploaded.

Changed in cloud-init (Ubuntu):
status: Fix Committed → Confirmed
Revision history for this message
Andreas Hasenack (ahasenack) wrote :

Please also confirm, via the test plan, that if the image has the snap deb installed, that the snaps will be upgraded, i.e., that we don't break the normal use case with canonical images.

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

Before release into updates, please make sure to address Oracular, and also the test plan amendment from comment #5.

Changed in cloud-init (Ubuntu Noble):
status: New → Fix Committed
tags: added: verification-needed verification-needed-noble
Revision history for this message
Andreas Hasenack (ahasenack) wrote : Please test proposed package

Hello Chad, or anyone else affected,

Accepted cloud-init into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud-init/24.1.3-0ubuntu3.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in cloud-init (Ubuntu Mantic):
status: New → Fix Committed
tags: added: verification-needed-mantic
Revision history for this message
Andreas Hasenack (ahasenack) wrote :

Hello Chad, or anyone else affected,

Accepted cloud-init into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud-init/24.1.3-0ubuntu1~23.10.4 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-mantic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in cloud-init (Ubuntu Jammy):
status: New → Fix Committed
tags: added: verification-needed-jammy
Revision history for this message
Andreas Hasenack (ahasenack) wrote :

Hello Chad, or anyone else affected,

Accepted cloud-init into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud-init/24.1.3-0ubuntu1~22.04.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in cloud-init (Ubuntu Focal):
status: New → Fix Committed
tags: added: verification-needed-focal
Revision history for this message
Andreas Hasenack (ahasenack) wrote :

Hello Chad, or anyone else affected,

Accepted cloud-init into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud-init/24.1.3-0ubuntu1~20.04.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Chad Smith (chad.smith)
description: updated
Chad Smith (chad.smith)
description: updated
Chad Smith (chad.smith)
summary: - images without snapd installed error on `update_packages: true` user-
+ images without snapd installed error on `upgrade_packages: true` user-
data
Revision history for this message
Chad Smith (chad.smith) wrote :

Sru validation script

Revision history for this message
Chad Smith (chad.smith) wrote :

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-proposed shortly cherry-picking this fix.

Revision history for this message
Chad Smith (chad.smith) wrote :

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-0ubuntu1~22.04.4
- focal: 24.1.3-0ubuntu1~20.04.4

Will SRU re-run verification script when these uploads are available in -proposed.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package cloud-init - 24.2~2g51c6569f-0ubuntu1

---------------
cloud-init (24.2~2g51c6569f-0ubuntu1) oracular; urgency=medium

  * Upstream snapshot based on upstream/main at 51c6569f.
    - Bugs fixed in this snapshot: (LP: #2064132)

 -- Chad Smith <email address hidden> Fri, 03 May 2024 15:34:25 -0600

Changed in cloud-init (Ubuntu Oracular):
status: Confirmed → Fix Released
Chad Smith (chad.smith)
tags: added: regression-proposed
Revision history for this message
Chad Smith (chad.smith) wrote :

This fix is also uploaded for SRU to noble in cloud-init version 24.1.3-0ubuntu3.2

tags: added: verification-failed-focal verification-failed-jammy verification-failed-mantic verification-failed-noble
removed: verification-needed-focal verification-needed-jammy verification-needed-mantic verification-needed-noble
tags: added: verification-failed
removed: verification-needed
Revision history for this message
Timo Aaltonen (tjaalton) wrote : Please test proposed package

Hello Chad, or anyone else affected,

Accepted cloud-init into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud-init/24.1.3-0ubuntu3.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

tags: added: verification-needed verification-needed-noble
removed: verification-failed verification-failed-noble
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Hello Chad, or anyone else affected,

Accepted cloud-init into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud-init/24.1.3-0ubuntu1~23.10.5 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-mantic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

tags: added: verification-needed-mantic
removed: verification-failed-mantic
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Hello Chad, or anyone else affected,

Accepted cloud-init into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud-init/24.1.3-0ubuntu1~22.04.4 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

tags: added: verification-needed-jammy
removed: verification-failed-jammy
tags: added: verification-needed-focal
removed: verification-failed-focal
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Hello Chad, or anyone else affected,

Accepted cloud-init into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud-init/24.1.3-0ubuntu1~20.04.4 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Revision history for this message
Chad Smith (chad.smith) wrote (last edit ):
Download full text (10.9 KiB)

==== focal SRU verification complete ===
csmith@downtown:~$ bash ./sru-2064132.sh
+ cat
+ cat
+ for SERIES in "focal"
+ 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 -- cloud-init status --wait
....................
status: done
+ lxc exec test-no-snap-focal -- apt-get update
Get:1 http://security.ubuntu.com/ubuntu focal-security InRelease [114 kB]
Hit:2 http://archive.ubuntu.com/ubuntu focal InRelease
Get:3 http://archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB]
Get:4 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages [2919 kB]
Get:5 http://security.ubuntu.com/ubuntu focal-security/main Translation-en [438 kB]
Get:6 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 Packages [2799 kB]
Get:7 http://archive.ubuntu.com/ubuntu focal-backports InRelease [108 kB]
Get:8 http://security.ubuntu.com/ubuntu focal-security/restricted Translation-en [391 kB]
Get:9 http://security.ubuntu.com/ubuntu focal-security/universe amd64 Packages [959 kB]
Get:10 http://security.ubuntu.com/ubuntu focal-security/universe Translation-en [202 kB]
Get:11 http://security.ubuntu.com/ubuntu focal-security/universe amd64 c-n-f Metadata [19.2 kB]
Get:12 http://security.ubuntu.com/ubuntu focal-security/multiverse amd64 Packages [24.0 kB]
Get:13 http://security.ubuntu.com/ubuntu focal-security/multiverse Translation-en [5904 B]
Get:14 http://security.ubuntu.com/ubuntu focal-security/multiverse amd64 c-n-f Metadata [548 B]
Get:15 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages [8628 kB]
Get:16 http://archive.ubuntu.com/ubuntu focal/universe Translation-en [5124 kB]
Get:17 http://archive.ubuntu.com/ubuntu focal/universe amd64 c-n-f Metadata [265 kB]
Get:18 http://archive.ubuntu.com/ubuntu focal/multiverse amd64 Packages [144 kB]
Get:19 http://archive.ubuntu.com/ubuntu focal/multiverse Translation-en [104 kB]
Get:20 http://archive.ubuntu.com/ubuntu focal/multiverse amd64 c-n-f Metadata [9136 B]
Get:21 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages [3296 kB]
Get:22 http://archive.ubuntu.com/ubuntu focal-updates/main Translation-en [521 kB]
Get:23 http://archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages [2916 kB]
Get:24 http://archive.ubuntu.com/ubuntu focal-updates/restricted Translation-en [407 kB]
Get:25 http://archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages [1185 kB]
Get:26 http://archive.ubuntu.com/ubuntu focal-updates/universe Translation-en [284 kB]
Get:27 http://archive.ubuntu.com/ubuntu focal-updates/universe amd64 c-n-f Metadata [25.7 kB]
Get:28 http://archive.ubuntu.com/ubuntu focal-updates/multiverse amd64 Packages [26.2 kB]
Get:29 http://archive.ubuntu.com/ubuntu focal-updates/multiverse Translation-en [7880 B]
Get:30 http://archive.ubuntu.com/ubuntu focal-updates/multiverse amd64 c-n-f Metadata [620 B]
Get:31 http://archive.ubuntu.com/ubuntu focal-backports/main amd64 Packages [45.7 kB]
Get:32 http://archive.ubuntu.com/ub...

Revision history for this message
Chad Smith (chad.smith) wrote :
Download full text (11.6 KiB)

=== 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-jammy
Starting test-no-snap-jammy
+ sleep 6
+ lxc exec test-no-snap-jammy -- cloud-init status --wait
..................
status: done
+ lxc exec test-no-snap-jammy -- apt-get update
Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease
Get:2 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
Get:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB]
Get:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [109 kB]
Get:5 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages [1427 kB]
Get:6 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages [14.1 MB]
Get:7 http://security.ubuntu.com/ubuntu jammy-security/main Translation-en [247 kB]
Get:8 http://security.ubuntu.com/ubuntu jammy-security/restricted amd64 Packages [1807 kB]
Get:9 http://security.ubuntu.com/ubuntu jammy-security/restricted Translation-en [307 kB]
Get:10 http://security.ubuntu.com/ubuntu jammy-security/universe amd64 Packages [852 kB]
Get:11 http://security.ubuntu.com/ubuntu jammy-security/universe Translation-en [164 kB]
Get:12 http://security.ubuntu.com/ubuntu jammy-security/universe amd64 c-n-f Metadata [16.8 kB]
Get:13 http://security.ubuntu.com/ubuntu jammy-security/multiverse amd64 Packages [37.2 kB]
Get:14 http://security.ubuntu.com/ubuntu jammy-security/multiverse Translation-en [7588 B]
Get:15 http://security.ubuntu.com/ubuntu jammy-security/multiverse amd64 c-n-f Metadata [260 B]
Get:16 http://archive.ubuntu.com/ubuntu jammy/universe Translation-en [5652 kB]
Get:17 http://archive.ubuntu.com/ubuntu jammy/universe amd64 c-n-f Metadata [286 kB]
Get:18 http://archive.ubuntu.com/ubuntu jammy/multiverse amd64 Packages [217 kB]
Get:19 http://archive.ubuntu.com/ubuntu jammy/multiverse Translation-en [112 kB]
Get:20 http://archive.ubuntu.com/ubuntu jammy/multiverse amd64 c-n-f Metadata [8372 B]
Get:21 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [1638 kB]
Get:22 http://archive.ubuntu.com/ubuntu jammy-updates/main Translation-en [307 kB]
Get:23 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packages [1864 kB]
Get:24 http://archive.ubuntu.com/ubuntu jammy-updates/restricted Translation-en [316 kB]
Get:25 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages [1074 kB]
Get:26 http://archive.ubuntu.com/ubuntu jammy-updates/universe Translation-en [245 kB]
Get:27 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 c-n-f Metadata [22.1 kB]
Get:28 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse amd64 Packages [42.7 kB]
Get:29 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse Translation-en [10.4 kB]
Get:30 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse amd64 c-n-f Metadata [472 B]
Get:31 http://archive.ubuntu.com/ubuntu jammy-backports/main amd64 Packages [67.1 kB]
Get:3...

Revision history for this message
Chad Smith (chad.smith) wrote :
Download full text (9.0 KiB)

==== 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-noble
Starting test-no-snap-noble
+ sleep 6
+ lxc exec test-no-snap-noble -- cloud-init status --wait
.....
status: done
+ lxc exec test-no-snap-noble -- apt-get update
Hit:1 http://archive.ubuntu.com/ubuntu noble InRelease
Get:2 http://security.ubuntu.com/ubuntu noble-security InRelease [89.7 kB]
Get:3 http://archive.ubuntu.com/ubuntu noble-updates InRelease [89.7 kB]
Get:4 http://archive.ubuntu.com/ubuntu noble-backports InRelease [89.7 kB]
Get:5 http://security.ubuntu.com/ubuntu noble-security/main amd64 Packages [26.7 kB]
Get:6 http://security.ubuntu.com/ubuntu noble-security/main Translation-en [8124 B]
Get:7 http://security.ubuntu.com/ubuntu noble-security/universe amd64 Packages [10.6 kB]
Get:8 http://security.ubuntu.com/ubuntu noble-security/universe Translation-en [4596 B]
Get:9 http://security.ubuntu.com/ubuntu noble-security/universe amd64 c-n-f Metadata [112 B]
Get:10 http://security.ubuntu.com/ubuntu noble-security/multiverse amd64 c-n-f Metadata [116 B]
Get:11 http://archive.ubuntu.com/ubuntu noble/universe amd64 Packages [15.0 MB]
Get:12 http://archive.ubuntu.com/ubuntu noble/universe Translation-en [5982 kB]
Get:13 http://archive.ubuntu.com/ubuntu noble/universe amd64 Components [3871 kB]
Get:14 http://archive.ubuntu.com/ubuntu noble/universe amd64 c-n-f Metadata [301 kB]
Get:15 http://archive.ubuntu.com/ubuntu noble/multiverse amd64 Packages [269 kB]
Get:16 http://archive.ubuntu.com/ubuntu noble/multiverse Translation-en [118 kB]
Get:17 http://archive.ubuntu.com/ubuntu noble/multiverse amd64 Components [35.0 kB]
Get:18 http://archive.ubuntu.com/ubuntu noble/multiverse amd64 c-n-f Metadata [8328 B]
Get:19 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages [28.4 kB]
Get:20 http://archive.ubuntu.com/ubuntu noble-updates/main Translation-en [8996 B]
Get:21 http://archive.ubuntu.com/ubuntu noble-updates/universe amd64 Packages [17.6 kB]
Get:22 http://archive.ubuntu.com/ubuntu noble-updates/universe Translation-en [6096 B]
Get:23 http://archive.ubuntu.com/ubuntu noble-updates/universe amd64 c-n-f Metadata [112 B]
Get:24 http://archive.ubuntu.com/ubuntu noble-updates/multiverse amd64 c-n-f Metadata [116 B]
Get:25 http://archive.ubuntu.com/ubuntu noble-backports/main amd64 c-n-f Metadata [112 B]
Get:26 http://archive.ubuntu.com/ubuntu noble-backports/universe amd64 Packages [3936 B]
Get:27 http://archive.ubuntu.com/ubuntu noble-backports/universe Translation-en [1392 B]
Get:28 http://archive.ubuntu.com/ubuntu noble-backports/universe amd64 c-n-f Metadata [116 B]
Get:29 http://archive.ubuntu.com/ubuntu noble-backports/restricted amd64 c-n-f Metadata [116 B]
Get:30 http://archive.ubuntu.com/ubuntu noble-backports/multiverse amd64 c-n-f Metadata [116 B]
Fetched 26.0 MB in 5s (5274 kB/s)
Reading package lists... Done
+ lxc exec test-no-snap-noble -- apt-get install cloud...

Read more...

tags: added: verification-done verification-done-focal verification-done-jammy verification-done-mantic
removed: verification-needed verification-needed-focal verification-needed-jammy verification-needed-mantic
tags: added: verification-done-noble
removed: verification-needed-noble
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.