Update google compute-image-packages to 20171006

Bug #1722356 reported by Balint Reczey
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gce-compute-image-packages (Ubuntu)
Fix Released
Undecided
Unassigned
Trusty
Fix Released
Undecided
Unassigned
Xenial
Fix Released
Undecided
Unassigned
Zesty
Fix Released
Undecided
Unassigned

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.

[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

Revision history for this message
Balint Reczey (rbalint) wrote :
Changed in gce-compute-image-packages (Ubuntu):
status: New → Incomplete
status: Incomplete → Confirmed
Revision history for this message
Balint Reczey (rbalint) wrote :

I have uploaded the package to this PPA:
https://launchpad.net/~rbalint/+archive/ubuntu/scratch/+packages

Also please see the debdiff attached.

Changes:
 gce-compute-image-packages (20171006+dfsg1-0ubuntu1) artful; urgency=medium
 .
   * List current packaging repository in debian/control
   * New upstream version 20171006+dfsg1 (LP: #1722356)
     - Fix system hang during VM shutdown
     - JSON parser accepts string types for int64 values
   * Update symlink to shared library with updated patch version

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

This bug was fixed in the package gce-compute-image-packages - 20171006+dfsg1-0ubuntu1

---------------
gce-compute-image-packages (20171006+dfsg1-0ubuntu1) artful; urgency=medium

  * List current packaging repository in debian/control
  * New upstream version 20171006+dfsg1 (LP: #1722356)
    - Fix system hang during VM shutdown
    - JSON parser accepts string types for int64 values
  * Update symlink to shared library with updated patch version

 -- Balint Reczey <email address hidden> Mon, 09 Oct 2017 19:16:04 +0200

Changed in gce-compute-image-packages (Ubuntu):
status: Confirmed → Fix Released
tags: added: id-59b19294844575c16763d1dd
Revision history for this message
Andy Whitcroft (apw) wrote : Please test proposed package

Hello Balint, or anyone else affected,

Accepted gce-compute-image-packages into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gce-compute-image-packages/20171006+dfsg1-0ubuntu1~17.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 and change the tag from verification-needed-zesty to verification-done-zesty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-zesty. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in gce-compute-image-packages (Ubuntu Zesty):
status: New → Fix Committed
tags: added: verification-needed verification-needed-zesty
Changed in gce-compute-image-packages (Ubuntu Xenial):
status: New → Fix Committed
tags: added: verification-needed-xenial
Revision history for this message
Andy Whitcroft (apw) wrote :

Hello Balint, or anyone else affected,

Accepted gce-compute-image-packages into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gce-compute-image-packages/20171006+dfsg1-0ubuntu1~16.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 and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in gce-compute-image-packages (Ubuntu Trusty):
status: New → Fix Committed
tags: added: verification-needed-trusty
Revision history for this message
Andy Whitcroft (apw) wrote :

Hello Balint, or anyone else affected,

Accepted gce-compute-image-packages into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gce-compute-image-packages/20171006+dfsg1-0ubuntu1~14.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 and change the tag from verification-needed-trusty to verification-done-trusty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-trusty. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Revision history for this message
Francis Ginther (fginther) wrote :

I have generated images and executed the CPC automated tests with no issues found. The images are available for additional testing:

Image Project
daily-ubuntu-lp1722356-1404-trusty-v20171016 ubuntu-os-cloud-devel
daily-ubuntu-lp1722356-1604-xenial-v20171011 ubuntu-os-cloud-devel
daily-ubuntu-lp1722356-1704-zesty-v20171011 ubuntu-os-cloud-devel

The CPC portion of the SRU verification is complete for all releases.

Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Google have reported some issues with this package so I'm marking it verification-failed.

tags: added: verification-failed-trusty verification-failed-xenial verification-failed-zesty
removed: verification-needed-trusty verification-needed-xenial verification-needed-zesty
tags: removed: verification-needed
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Testing of this version has been done with the new snapshot, marking as verification-done.

tags: added: verification-done-trusty verification-done-xenial verification-done-zesty
removed: verification-failed-trusty verification-failed-xenial verification-failed-zesty
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gce-compute-image-packages - 20171019+dfsg1-0ubuntu1~17.04.0

---------------
gce-compute-image-packages (20171019+dfsg1-0ubuntu1~17.04.0) zesty; urgency=medium

  [ Balint Reczey ]
  * New upstream version 20171019+dfsg1 (LP: #1726810)
    - Add status option for google_oslogin_control
    - OS Login activation via the accounts daemon
  * Tidy up d/control with the help of cme fix dpkg-control
  * Update symlink to shared library with updated minor version
  * Change package priority to optional from extra
  * Add debhelper token to prerm

  [ Zach Marano from Google Cloud Team ]
  * Depend on chrony | ntp | time-daemon instead of just ntp
  * Move all service activation handling to
    gce-compute-image-packages.{postinst|prerm}
  * Make google-compute-engine depend on google-compute-engine-oslogin

  [ Łukasz 'sil2100' Zemczak ]
  * Backport to zesty.

 -- Balint Reczey <email address hidden> Tue, 24 Oct 2017 16:35:46 +0200

Changed in gce-compute-image-packages (Ubuntu Zesty):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gce-compute-image-packages - 20171019+dfsg1-0ubuntu1~16.04.0

---------------
gce-compute-image-packages (20171019+dfsg1-0ubuntu1~16.04.0) xenial; urgency=medium

  [ Balint Reczey ]
  * New upstream version 20171019+dfsg1 (LP: #1726810)
    - Add status option for google_oslogin_control
    - OS Login activation via the accounts daemon
  * Tidy up d/control with the help of cme fix dpkg-control
  * Update symlink to shared library with updated minor version
  * Change package priority to optional from extra
  * Add debhelper token to prerm

  [ Zach Marano from Google Cloud Team ]
  * Depend on chrony | ntp | time-daemon instead of just ntp
  * Move all service activation handling to
    gce-compute-image-packages.{postinst|prerm}
  * Make google-compute-engine depend on google-compute-engine-oslogin

  [ Łukasz 'sil2100' Zemczak ]
  * Backport to xenial.

 -- Balint Reczey <email address hidden> Tue, 24 Oct 2017 16:35:46 +0200

Changed in gce-compute-image-packages (Ubuntu Xenial):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gce-compute-image-packages - 20171019+dfsg1-0ubuntu1~14.04.0

---------------
gce-compute-image-packages (20171019+dfsg1-0ubuntu1~14.04.0) trusty; urgency=medium

  [ Balint Reczey ]
  * New upstream version 20171019+dfsg1 (LP: #1726810)
    - Add status option for google_oslogin_control
    - OS Login activation via the accounts daemon
  * Tidy up d/control with the help of cme fix dpkg-control
  * Update symlink to shared library with updated minor version
  * Change package priority to optional from extra
  * Add debhelper token to prerm

  [ Zach Marano from Google Cloud Team ]
  * Depend on chrony | ntp | time-daemon instead of just ntp
  * Move all service activation handling to
    gce-compute-image-packages.{postinst|prerm}
  * Make google-compute-engine depend on google-compute-engine-oslogin

  [ Łukasz 'sil2100' Zemczak ]
  * Backport to trusty.
    - Retain the delta between devel and trusty as those are necessary for the
      package to build and work.

 -- Balint Reczey <email address hidden> Tue, 24 Oct 2017 16:35:46 +0200

Changed in gce-compute-image-packages (Ubuntu Trusty):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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