Ubuntu
google-compute-engine-oslogin package

Update d/control file with a dependency on google-guest-agent

Bug #2052438 reported by Chloé Smith
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
google-compute-engine-oslogin (Ubuntu)
Fix Released
Undecided
Chloé Smith
Xenial
New
Undecided
Unassigned
Bionic
New
Undecided
Unassigned
Focal
Fix Released
Undecided
Unassigned
Jammy
Fix Released
Undecided
Unassigned
Mantic
Fix Released
Undecided
Unassigned

Bug Description

[SRU]
=======

[Impact]

`google-compute-engine-oslogin` is a package provided by Google for installation within guests that run on Google Compute Engine (GCE). It is part of a collection of tools and daemons that ensure that Ubuntu images published to GCE run properly on the platform.

In Google's packed upstream debian distro `d/control` files for both `google-compute-engine-oslogin` and `google-guest-agent` there is a dependency on the other. This was not reflected in the ubuntu archive. LP: #2050956 fixed `google-guest-agent`'s dependency on `google-compute-engine-oslogin`, so now it's time to do the reverse. The regression caused in `google-guest-agent` was critical enough to warrant this stand-alone update into `google-compute-engine-oslogin`, and not just wait for it to be packaged into a normal update.

[Test Case]

When the 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
 * 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.
 * Each test image will be launched, and we will validate:
 ** the package version(s)
 ** that the correct ssh keys have been imported
 ** that the google specific services are running successfully

If all the testing indicates that the image containing the new package is acceptable, verification will be considered to be done.

[ Regression potential / Where problems could occur ]

As this is just a dependency change and not a functionality change, the risk is somewhat lower. That being said:

* In the edge case that a user has uninstalled/removed `google-guest-agent`, any
  update to install new versions of `google-compute-engine-oslogin` will force
  an installation of the guest-agent. But the guest-agent package is pretty
  fundamental to getting images working on the platform, so I don't think this
  is a viable set up anyways to be honest.

* There is also risk we might break users who have pinned a much older version
  of `google-guest-agent`. However, there has been a *significant* shift in
  functionality between these two packages (see LP: #2050956 for details) so we
  might actually be saving these pinned users from a bigger issue later...

[Additional Information]

This bug is used to track the release of this new version for all the supported suites, as per the policy mentioned here [0].

[0]: https://wiki.ubuntu.com/google-compute-engine-oslogin-Updates

See original description
Chloé Smith (kajiya)
Changed in google-compute-engine-oslogin (Ubuntu):
assignee: nobody → Chloé Smith (kajiya)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package google-compute-engine-oslogin - 20231004.00-0ubuntu2

---------------
google-compute-engine-oslogin (20231004.00-0ubuntu2) noble; urgency=medium

  * d/control: There must be a dependency on `google-guest-agent`
    to match the (upstream) Google managed d/control file (LP: #2052438)

 -- Chloé 'kajiya' Smith <email address hidden> Thu, 01 Feb 2024 00:06:38 +0000

Changed in google-compute-engine-oslogin (Ubuntu):
status: New → Fix Released
Chloé Smith (kajiya)
description: updated
Chloé Smith (kajiya)
description: updated
Chloé Smith (kajiya)
description: updated
Revision history for this message
Timo Aaltonen (tjaalton) wrote : Please test proposed package

Hello Chloé, or anyone else affected,

Accepted google-compute-engine-oslogin into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/google-compute-engine-oslogin/20231004.00-0ubuntu1~23.10.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-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 google-compute-engine-oslogin (Ubuntu Mantic):
status: New → Fix Committed
tags: added: verification-needed verification-needed-mantic
Changed in google-compute-engine-oslogin (Ubuntu Jammy):
status: New → Fix Committed
tags: added: verification-needed-jammy
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Hello Chloé, or anyone else affected,

Accepted google-compute-engine-oslogin into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/google-compute-engine-oslogin/20231004.00-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 google-compute-engine-oslogin (Ubuntu Focal):
status: New → Fix Committed
tags: added: verification-needed-focal
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Hello Chloé, or anyone else affected,

Accepted google-compute-engine-oslogin into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/google-compute-engine-oslogin/20231004.00-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.

Revision history for this message
Andrew Cloke (andrew-cloke) wrote :

As outlined in the [Test Case] for mantic and jammy:

 * Images have been built with these packages from the -proposed pocket and
   published in the `ubuntu-os-cloud-image-proposed` project
 * The images have gone through CPC's own CTF framework and testing has been successful
 * The images have been shared with the Google team and their testing has also been successful

The Google's team testing of the focal images is still ongoing.

tags: added: verification-done-jammy verification-done-mantic
removed: verification-needed-jammy verification-needed-mantic
Revision history for this message
Andrew Cloke (andrew-cloke) wrote :

As outlined in the [Test Case] for focal:

 * Images have been built with these packages from the -proposed pocket and
   published in the `ubuntu-os-cloud-image-proposed` project
 * The images have gone through CPC's own CTF framework and testing has been successful
 * The images have been shared with the Google team and their testing has also been successful

tags: added: verification-done verification-done-focal
removed: verification-needed verification-needed-focal
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package google-compute-engine-oslogin - 20231004.00-0ubuntu1~23.10.3

---------------
google-compute-engine-oslogin (20231004.00-0ubuntu1~23.10.3) mantic; urgency=medium

  * d/control: There must be a dependency on `google-guest-agent`
    to match the (upstream) Google managed d/control file (LP: #2052438)

 -- Chloé 'kajiya' Smith <email address hidden> Tue, 06 Feb 2024 13:18:51 +0000

Changed in google-compute-engine-oslogin (Ubuntu Mantic):
status: Fix Committed → Fix Released
Revision history for this message
Andreas Hasenack (ahasenack) wrote : Update Released

The verification of the Stable Release Update for google-compute-engine-oslogin has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

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

This bug was fixed in the package google-compute-engine-oslogin - 20231004.00-0ubuntu1~22.04.3

---------------
google-compute-engine-oslogin (20231004.00-0ubuntu1~22.04.3) jammy; urgency=medium

  * d/control: There must be a dependency on `google-guest-agent`
    to match the (upstream) Google managed d/control file (LP: #2052438)

 -- Chloé 'kajiya' Smith <email address hidden> Tue, 06 Feb 2024 14:06:11 +0000

Changed in google-compute-engine-oslogin (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Andreas Hasenack (ahasenack) wrote :

I'm trying to understand and sortout a component mismatch that this update is introducing in focal. Apparently you guys stopped building bin:google-compute-engine-oslogin from src:gce-compute-images-packages a while back, and now it's src:google-compute-engine-oslogin that builds bin:google-compute-engine-oslogin.

But the former was in main in focal, and it can't depend on bin:google-guest-agent which is in universe. And britney is complaining loudly[1]:

Migration status for google-compute-engine-oslogin (20231004.00-0ubuntu1~20.04.2 to 20231004.00-0ubuntu1~20.04.3): BLOCKED: Rejected/violates migration policy/introduces a regression
Issues preventing migration:
google-compute-engine-oslogin/amd64 in main cannot depend on google-guest-agent in universe
google-compute-engine-oslogin/arm64 in main cannot depend on google-guest-agent in universe
google-compute-engine-oslogin/armhf in main cannot depend on google-guest-agent in universe
google-compute-engine-oslogin/ppc64el in main cannot depend on google-guest-agent in universe
google-compute-engine-oslogin/s390x in main cannot depend on google-guest-agent in universe
Impossible Depends: google-compute-engine-oslogin -> google-guest-agent/20231004.02-0ubuntu1~20.04.3/amd64
Impossible Depends: google-compute-engine-oslogin -> google-guest-agent/20231004.02-0ubuntu1~20.04.3/arm64
Impossible Depends: google-compute-engine-oslogin -> google-guest-agent/20231004.02-0ubuntu1~20.04.3/armhf
Impossible Depends: google-compute-engine-oslogin -> google-guest-agent/20231004.02-0ubuntu1~20.04.3/ppc64el
Impossible Depends: google-compute-engine-oslogin -> google-guest-agent/20231004.02-0ubuntu1~20.04.3/s390x

1. https://ubuntu-archive-team.ubuntu.com/proposed-migration/focal/update_excuses.html#google-compute-engine-oslogin

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

google-guest-agent was promoted to main to fix this. When [1] clears, then the focal update can be released.

1. https://ubuntu-archive-team.ubuntu.com/proposed-migration/focal/update_excuses.html#google-compute-engine-oslogin

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

That has cleared.

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

This bug was fixed in the package google-compute-engine-oslogin - 20231004.00-0ubuntu1~20.04.3

---------------
google-compute-engine-oslogin (20231004.00-0ubuntu1~20.04.3) focal; urgency=medium

  * d/control: There must be a dependency on `google-guest-agent`
    to match the (upstream) Google managed d/control file (LP: #2052438)

 -- Chloé 'kajiya' Smith <email address hidden> Tue, 06 Feb 2024 16:16:42 +0000

Changed in google-compute-engine-oslogin (Ubuntu Focal):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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