Hello Chloé, or anyone else affected,
Accepted gce-compute-image-packages into noble-proposed. The package
will build now and be available at
https://launchpad.net/ubuntu/+source/gce-compute-image-
packages/20241010.00-0ubuntu1~24.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-
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: gce-compute-image-packages (Ubuntu Jammy)
Status: New => Fix Committed
** Tags added: verification-needed-jammy
--
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/2084486
Title:
Please update to 20241010.00
Status in gce-compute-image-packages package in Ubuntu:
Fix Released
Status in gce-compute-image-packages source package in Focal:
Incomplete
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
Status in gce-compute-image-packages source package in Plucky:
Fix Released
Bug description:
Following on from previous similar package update requests @ LP:
#2073164, LP: #2066314, LP: #2033061 and LP: #2020770 this bug is a
request to update gce-compute-image-packages to the upstream version
`20241010.00` @ https://github.com/GoogleCloudPlatform/guest-
configs/releases/tag/20241010.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 their 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-devel project
* 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 internal image validation.
If all the testing indicates that the image containing the new package
is acceptable, verification will be considered to be done.
[Vendored Dependencies]
There were no vendoring changes in these releases (OO/NN/JJ/FF)
[Where Problems Could Occur]
There are many upstream changes in `20241010.00-0ubuntu1` vs.
`20240607.00-0ubuntu1`; however between the guest-test-infra 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`
That being said, there are changes to the `pre-inst` and edits to how
the instance hostname is created/validated. There are also significant
changes to network config management, OSLogin, SSH access and
networkctl/dhclient in this bug's "sister" at LP: #2084498. We should
be mindful of all these changes as they could possibly cause instances
to become inaccessible. To mitigate this there are several CTF suites
that will trigger an instance reboot (e.g. google_disk_size,
google_shutdown_script, google_shutdown_script_url, etc.). There is
also a specific job we have internally that will create an instance
from a "normal" image, and gradually install each guest-agent package
from -proposed with reboots in between. Assuming all this works as
expected we can be assured we've mitigated.
[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
The updated package is not built for armhf and riscv64 due to upstream
regressions but the package is not used on those architectures thus
please release the SRU without the armhf and risc64 binaries.
The package does not build for powerpc on Xenial, but this is OK since
it is not used on powerpc either.
[0]: https://github.com/GoogleCloudPlatform/guest-test-infra
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/2084486/+subscriptions