[Bug 2052438] Re: Update d/control file with a dependency on google-guest-agent

[Andreas Hasenack]

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

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to google-compute-engine-oslogin
in Ubuntu.
https://bugs.launchpad.net/bugs/2052438

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

Status in google-compute-engine-oslogin package in Ubuntu:
  Fix Released
Status in google-compute-engine-oslogin source package in Xenial:
  New
Status in google-compute-engine-oslogin source package in Bionic:
  New
Status in google-compute-engine-oslogin source package in Focal:
  Fix Committed
Status in google-compute-engine-oslogin source package in Jammy:
  Fix Released
Status in google-compute-engine-oslogin source package in Mantic:
  Fix Released

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/google-compute-engine-oslogin/+bug/2052438/+subscriptions