[Bug 2106195] Please test proposed package
Andreas Hasenack
2106195 at bugs.launchpad.net
Wed Apr 30 13:41:39 UTC 2025
Hello Chloé, or anyone else affected,
Accepted gce-compute-image-packages into focal-proposed. The package
will build now and be available at
https://launchpad.net/ubuntu/+source/gce-compute-image-
packages/20250328.00-0ubuntu2~20.04.0 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.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gce-compute-image-packages in
Ubuntu.
https://bugs.launchpad.net/bugs/2106195
Title:
[SRU] [FFe] Please update to 20250328.00
Status in gce-compute-image-packages package in Ubuntu:
Fix Released
Status in gce-compute-image-packages source package in Focal:
Fix Committed
Status in gce-compute-image-packages source package in Jammy:
Fix Committed
Status in gce-compute-image-packages source package in Noble:
Fix Committed
Status in gce-compute-image-packages source package in Oracular:
Fix Committed
Bug description:
==== FFe
Please except this version for plucky before the release. catred
provides good detail here [0], but essentially version
20250107.00-0ubuntu1 in plucky affects cloud-init due to newly
included systemd-networkd hooks. A user attempting to set their
hostname via cloud-init will no longer get the expected hostname, but
rather the internal default hostname set by Google. For any users
upgrading to plucky who are using cloud-init with a large fleet, this
would be a breaking change.
It also (selfishly) would help CPC a lot to get this new version in
quickly. There are 2 other SRUs (LP: #2096765 && LP: #2096657) blocked
until this new version here can also be SRU-ed (as we validate all the
Google guest packages "wholesale" due to their interplay).
[0]: https://bugs.launchpad.net/ubuntu/+source/google-guest-
agent/+bug/2096765/comments/19
########### SRU
==== Bug
Following on from similar package update requests @ LP: #2084486, LP:
#2073164, LP: #2066314 and LP: #2033061, this bug is a request to
update gce-compute-image-packages to the upstream version
`20250328.00` @ https://github.com/GoogleCloudPlatform/guest-
configs/releases/tag/20250328.00
This package has an SRU exception @
https://wiki.ubuntu.com/StableReleaseUpdates#gce-compute-image-
packages including an ageing exception detailed @
https://wiki.ubuntu.com/gce-compute-image-packages-Updates
[Impact]
This package is provided by Google for installation within guests that
run on Google Compute Engine. It is part of a collection of tools and
daemons, that ensure that the Ubuntu images published to GCE run
properly on their platform.
Cloud platforms evolve at a rate that can't be handled in six-month
increments, and they will often develop features that they would like
to be available to customers who don't want to upgrade from earlier
Ubuntu releases. As such, updating this package to more recent
upstream releases is required within all Ubuntu releases, so they
continue to function properly in the GCP environment.
[Test Case]
When a new version of this package is uploaded to -proposed, the
following will happen:
* an image based on -proposed will be built for GCE and published to the ubuntu-os-cloud-image-proposed project
* the CPC team will run internal validations (CTF) and Google's upstream test suite `cloud-image-tests` (CIT)
* the GCE team will be asked to validate that the new package addresses the issues it is expected to address, and that the image passes their own internal image validation.
We will also re-validate that this new version does not have the
regression introduced by 20250107.00-0ubuntu1 (LP: #2096762, not SRU-
ed)
If all the testing indicates that the new package is acceptable,
verification can be considered done.
[Vendored Dependencies]
N/A for gce-compute-image-packages
[Where Problems Could Occur]
There are some minor upstream changes in `20250328.00-ubuntu1` vs.
`20250107.00-0ubuntu1`; however between the cloud-image-tests suite
[0] (which is run for validation by CPC _and_ Google) and CPC's own
internal test harness (CTF), there is confidence that most if not all
"edge cases" and/or obvious regressions concerns can be dismissed
before the new version lands in `-updates`.
[Other Information]
This bug is used for tracking of releasing the new upstream version
for all supported series, as per the approved policy mentioned in the
following MRE:
https://wiki.ubuntu.com/gce-compute-image-packages-Updates
This package is only used for AMD64 and ARM64 but is built for all
available architectures.
[0]: https://github.com/GoogleCloudPlatform/cloud-image-tests
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/2106195/+subscriptions
More information about the foundations-bugs
mailing list