[Bug 1792466] Re: Update google compute-image-packages to 20180905

Balint Reczey balint.reczey at canonical.com
Fri Oct 19 12:49:57 UTC 2018


The latest upload did not change the package related to this package
just included the bug number in .changes accidentally. Marking
verification as done for the affected releases.

** Tags removed: verification-needed verification-needed-trusty verification-needed-xenial
** Tags added: verification-done verification-done-trusty verification-done-xenial

-- 
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/1792466

Title:
   Update google compute-image-packages to 20180905

Status in gce-compute-image-packages package in Ubuntu:
  Fix Released
Status in gce-compute-image-packages source package in Trusty:
  Fix Committed
Status in gce-compute-image-packages source package in Xenial:
  Fix Committed
Status in gce-compute-image-packages source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  compute-image-packages is provided by Google for installation within
  guests that run on Google Compute Engine. It is a collection of tools
  and daemons, packaged as gce-compute-image-packages, 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 gce-compute-image-packages to more
  recent upstream releases is required within all Ubuntu releases, so
  they continue to function properly in their environment.

  With this release we also add a new binary package to the suite -
  google-compute-engine-oslogin which is for a future feature of using
  OS Login on GCE VM instances.

  In the SRU for Trusty the maintainer scripts removed manual handling
  of systemd services because systemd can be present on Trusty systemd
  due to recent changes.

  In the Trusty SRU the maintainer scripts are also changed to
  start/restart the shipped upstart jobs and also running
  google_instance_setup.

  [Test Case]

  When a new version of gce-compute-image-packages is uploaded to
  -proposed, the following will be done:

   * an image based on -proposed will be built for GCE and published to the ubuntu-os-cloud-devel project
   * the CPC team will write new automated tests to cover new testable functionality (if any) in the new package
   * the automated testing that the CPC team normally runs against GCE images before they are published will be run against the -proposed image
   * 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.

  [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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1792466/+subscriptions



More information about the foundations-bugs mailing list