Please update to upstream release 20220824.00

-google-osconfig-agent (20210608.1-0ubuntu3) jammy; urgency=medium

Why does the uploaded version not inherit from the version currently in jammy?

It's not ideal that ubuntu2 and ubuntu3 are removed from the changelog, but I don't consider that blocking (as those were no-change rebuilds). But I do have a different question:

I see the changelog mention "Update vendored google.golang.org/genproto", and I see that in the diff - but it seems like... the vendored genproto is actually downgraded? Diff in kinetic shows changes of copyright dates from 2020 to 2018, same for some of the version numbers. Why is the vendored bit being downgraded, even though the changelog mentions update? What is the reason? Is it just confused diff or what?

This bug was fixed in the package google-osconfig-agent - 20220824.00-0ubuntu1

---------------
google-osconfig-agent (20220824.00-0ubuntu1) lunar; urgency=medium

  * New upstream version 20220824.00. (LP: #1996735)
  * Update vendored google.golang.org/genproto.
  * Override deb build settings for 1.16+ compatibility.
  * Deprecate old config directory in favor of new cache directory.
  * Install var/lib/google_osconfig_agent directory.

 -- Utkarsh Gupta <email address hidden> Thu, 10 Nov 2022 17:13:49 +0530

Hello Steve,

> -google-osconfig-agent (20210608.1-0ubuntu3) jammy; urgency=medium
>
> Why does the uploaded version not inherit from the version currently
> in jammy?

Aah, I maintain a git repository for Google guest agents and generally manage everything there. I did quickly look if there's anything different in the archive content-wise but we had the same version and forgot to incorporate the d/ch entries. Hope that's not really a problem? If you'd like I can re-build and upload with the 2 d/ch entries in?

Or, I can just update my git repository with the d/ch entries and the next time we SRU back to Jammy, they'll be in. Either way works for me. Let me know what you think. TIA.

Hi Lukasz,

> I see the changelog mention "Update vendored google.golang.org/genproto",
> and I see that in the diff - but it seems like... the vendored genproto
> is actually downgraded? Diff in kinetic shows changes of copyright dates
> from 2020 to 2018, same for some of the version numbers. Why is the
> vendored bit being downgraded, even though the changelog mentions
> update? What is the reason? Is it just confused diff or what?

AFAIK, it's still an "update" if you closely look at the small portion of the diff (just to give you an idea):

-// protoc-gen-go v1.25.0
-// protoc v3.13.0
+// protoc-gen-go v1.26.0
+// protoc v3.12.2

..the protoc-gen-go version is bieng bumped from 1.25 to 1.26 (however protoc is being downgraded and so is the copyright entries). This is maintained by Google - I can't seem to find an obvious reason behind the change (nor could diff that out in the upstream changelog) but if you think it's a blocker, I can reach out to them and tell you the exact reason?

P.S. I am not sure if that's really a huge thing but of course, your concerns are fair and valid and you're far more experienced in this anyway. ;)

Let me know what you think?

Thank you for your follow up comment. This is fine. I'll accept those into -proposed - a small stylistic thing I noticed though was in debian/postrm where at least in the diff the two touch lines used different whitespace indents.

Hello Utkarsh, or anyone else affected,

Accepted google-osconfig-agent into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/google-osconfig-agent/20220824.00-0ubuntu1~22.10.1 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-kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. 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.

Hello Utkarsh, or anyone else affected,

Accepted google-osconfig-agent into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/google-osconfig-agent/20220824.00-0ubuntu1~22.04.1 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.

Hello Utkarsh, or anyone else affected,

Accepted google-osconfig-agent into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/google-osconfig-agent/20220824.00-0ubuntu1~20.04.1 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.

Hello Utkarsh, or anyone else affected,

Accepted google-osconfig-agent into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/google-osconfig-agent/20220824.00-0ubuntu1~18.04.1 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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. 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.

All autopkgtests for the newly accepted google-osconfig-agent (20220824.00-0ubuntu1~22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

google-osconfig-agent/20220824.00-0ubuntu1~22.04.1 (armhf)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy/update_excuses.html#google-osconfig-agent

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

All autopkgtests for the newly accepted google-osconfig-agent (20220824.00-0ubuntu1~22.10.1) for kinetic have finished running.
The following regressions have been reported in tests triggered by the package:

google-osconfig-agent/20220824.00-0ubuntu1~22.10.1 (arm64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/kinetic/update_excuses.html#google-osconfig-agent

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

I re-triggered the autopkgtest and it's passing now. So no real regression. \o/

The focal upload is failing to build on ppc64el: https://launchpad.net/ubuntu/+source/google-osconfig-agent/20220824.00-0ubuntu1~20.04.1/

Hiya. I just re-triggered the failing build and it's now passing. So all good now. \o/

Hey SRU folks o/
Due to the completion of Google's testing and CPC's own verification, I'm marking verification-complete for all these releases.

## Notes

Testing the new Google guest agents was primarily performed by Google themselves. They have now given a +1 to proceed. In addition, these images have gone through testing from the CPC team (using CTF).

From my own testing, images were produced with the guest agents directly from proposed and uploaded to GCE (the same images that Google used in their own testing).

## What was verified

1) The version of google-compute-engine-oslogin
2) Expected services were running and had completed successfully

# Bionic
Version: 20220824.00-0ubuntu1~18.04.1
systemctl status google-osconfig-agent
● google-osconfig-agent.service - Google OSConfig Agent
   Loaded: loaded (/lib/systemd/system/google-osconfig-agent.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2023-01-19 19:58:03 UTC; 54min ago
 Main PID: 1502 (google_osconfig)
    Tasks: 10 (limit: 4660)
   CGroup: /system.slice/google-osconfig-agent.service
           └─1502 /usr/bin/google_osconfig_agent

Jan 19 19:58:03 bionic-google-oslogin-test OSConfigAgent[1502]: 2023-01-19T19:58:03.7465Z OSConfigAgent Info: O
Jan 19 19:58:03 bionic-google-oslogin-test systemd[1]: Started Google OSConfig Agent.

# Focal
Version: 20220824.00-0ubuntu1~20.04.1
systemctl status google-osconfig-agent
● google-osconfig-agent.service - Google OSConfig Agent
     Loaded: loaded (/lib/systemd/system/google-osconfig-agent.service; enabled; vendor preset: enabled)
     Active: active (running) since Thu 2023-01-19 19:56:50 UTC; 57min ago
   Main PID: 600 (google_osconfig)
      Tasks: 10 (limit: 4694)
     Memory: 23.9M
     CGroup: /system.slice/google-osconfig-agent.service
             └─600 /usr/bin/google_osconfig_agent

Jan 19 19:56:50 focal-google-oslogin-test systemd[1]: Started Google OSConfig Agent.
Jan 19 19:56:50 focal-google-oslogin-test OSConfigAgent[600]: 2023-01-19T19:56:50.5722Z OSConfigAgent Info: OSConfig Agent (version 20220824.00-0ubuntu1~20.04.1) started.

# Jammy
Version: 20220824.00-0ubuntu1~22.04.1
systemctl status google-osconfig-agent
● google-osconfig-agent.service - Google OSConfig Agent
     Loaded: loaded (/lib/systemd/system/google-osconfig-agent.service; enabled; vendor preset: enabled)
     Active: active (running) since Thu 2023-01-19 18:49:17 UTC; 2h 5min ago
   Main PID: 581 (google_osconfig)
      Tasks: 8 (limit: 4694)
     Memory: 22.2M
        CPU: 1.347s
     CGroup: /system.slice/google-osconfig-agent.service
             └─581 /usr/bin/google_osconfig_agent

Jan 19 18:49:17 jammy-google-oslogin-test OSConfigAgent[581]: 2023-01-19T18:49:17.5968Z OSConfigAgent Info: OSConfig Agent (version 20220824.00-0ubuntu1~22.04.1) started.
Jan 19 18:49:17 jammy-google-oslogin-test systemd[1]: Started Google OSConfig Agent.

# Kinetic
Version: 20220824.00-0ubuntu1~22.10.1
systemctl status google-osconfig-agent
● google-osconfig-agent.service - Google OSConfig Agent
     Loaded: loaded (/lib/systemd/system/google-osconfig-agent.service; enabled; preset: enabled)
     Active: active (running) since Thu 2023-01-1...

Hey! Thank you for the verification of the package. However, it seems that the new update FTBFS on s390x (even though it built fine previously). Not sure how relevant it is:
https://launchpad.net/ubuntu/+source/google-osconfig-agent/20220824.00-0ubuntu1~22.10.1/+build/24865918
(and build log here: https://launchpadlibrarian.net/635689745/buildlog_ubuntu-kinetic-s390x.google-osconfig-agent_20220824.00-0ubuntu1~22.10.1_BUILDING.txt.gz)

I'll restart the build and see if a re-run helps.

It passed now. Yay.

This bug was fixed in the package google-osconfig-agent - 20220824.00-0ubuntu1~22.10.1

---------------
google-osconfig-agent (20220824.00-0ubuntu1~22.10.1) kinetic; urgency=medium

  * No-change rebuild for Kinetic. (LP: #1996735)

 -- Utkarsh Gupta <email address hidden> Thu, 17 Nov 2022 15:22:55 +0530

The verification of the Stable Release Update for google-osconfig-agent 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.

This bug was fixed in the package google-osconfig-agent - 20220824.00-0ubuntu1~22.04.1

---------------
google-osconfig-agent (20220824.00-0ubuntu1~22.04.1) jammy; urgency=medium

  * No-change rebuild for Jammy. (LP: #1996735)

 -- Utkarsh Gupta <email address hidden> Thu, 17 Nov 2022 18:18:30 +0530

This bug was fixed in the package google-osconfig-agent - 20220824.00-0ubuntu1~20.04.1

---------------
google-osconfig-agent (20220824.00-0ubuntu1~20.04.1) focal; urgency=medium

  * No-change rebuild for Focal. (LP: #1996735)

 -- Utkarsh Gupta <email address hidden> Thu, 17 Nov 2022 19:19:29 +0530

This bug was fixed in the package google-osconfig-agent - 20220824.00-0ubuntu1~18.04.1

---------------
google-osconfig-agent (20220824.00-0ubuntu1~18.04.1) bionic; urgency=medium

  * No-change rebuild for Bionic. (LP: #1996735)

 -- Utkarsh Gupta <email address hidden> Thu, 17 Nov 2022 19:27:18 +0530