This bug was fixed in the package google-guest-agent -
20260819.00+~20260819.00-0ubuntu1
---------------
google-guest-agent (20260819.00+~20260819.00-0ubuntu1) stonking; urgency=medium
* New upstream release for 20260819.00 (LP: #2164943)
* This package is now built from both of Google's agent
repositories at their (currently matching) `20260819.00`
tags:
* guest-agent (the old, "classic" agent) as the main
orig tarball
* google-guest-agent (the new plugin manager, confusingly
named the same as the source package...) as a component
orig tarball that `dpkg-source` unpacks into
`./google-guest-agent/`
* d/copyright
* Regenerated from scratch to cover both the repos and both
vendored golang trees. Also picks up the `THIRD_PARTY_LICENSES/`
files that the old file missed entirely and clear the old
`superfluous-file-pattern` lint warnings
* d/extra/vendor-google-guest-agent/ is the new vendored golang
dependency tree for the new plugin manager repository
* Also a re-vendor of d/extra/vendor/ for the new
`guest-agent` release
* d/google-guest-agent.postinst
* Stop and disable the legacy units when upgrading from a
pre-plugin manager pkg
* Seed `/etc/google-guest-agent/core-plugin-enabled` as
"true" (without overriding the user's choice, if any)
* d/google-guest-agent.postrm
* Take the `core-plugin-enabled` state file away again on uninstall
`postinst` writes it again manually so `dpkg` doesn't track it
and therefore won't tidy it up for us
* Drop the `/etc/google-guest-agent/` dir as well if it's empty
* d/install: install the systemd units into `/usr/lib/systemd/system`
rather than the old `/lib` alias to fix that long running
lintian error
* d/patches: refresh `fix-startup-script-ordering.patch` and
`0005-make-service-directive-explicit.patch` which had drifted
now that upstream orders `google-startup-scripts.service`
_after_ `google-guest-agent-manager.service`
* d/source/include-binaries
* Refreshed as the `s2a-go` test certs are no longer vendored
(only `protobuf`'s `editions_defaults.binpb` from each of
the two vendor trees are still vendored)
* d/README.source
* Document this new two repo layout, the new `uscan` workflow
and the new vendoring procedure we should use going forward now
* d/watch
* Now tracks both repos, the second stanza uses
`component=google-guest-agent` and both stanzas use
the `group` version policy so each repo is tracked at
its own newest tag. `uscan` joins the two tags with a `+~`
to build the version (e.g. `20260819.00+~20260820.00` for
"classic" `20260819.00` plus new plugin manager `20260820.00`)
and names both orig tarballs after that composite. So if Google
ever diverge the two repo tags (I strongly suspect the matching
tags this time are just a coincidence) both tags stay visible in
the version
* Both tarballs are now plain old `uscan` downloads. Neither
needs repacking by hand, or pinning to a bare git commit hash,
because upstream now actually has tags in the new plugin manager
repo (and they ship the generated *.pb.go files)
* d/rules
* Builds and installs the following plugin manager binaries:
* google_guest_agent_manager
* google_guest_compat_manager
* gce_metadata_script_runner
* gce_compat_metadata_script_runner
* core_plugin (into `GuestAgentCorePlugin/`, see below)
* ggactl_plugin
* The ggactl_plugin_cleanup alias (and the `/usr/sbin`
compatibility symlinks)
* Install the core plugin as
`/usr/lib/google/guest_agent/GuestAgentCorePlugin/core_plugin`
alongside its upstream `manifest.binpb`. The plugin manager
discovers local plugins by scanning for `$PLUGIN/manifest.binpb`
and then launches the absolute `entry_point` recorded in that
manifest
* Build and ship the two bundled local plugin extensions,
each in their own directory next to their manifests:
* `GuestTelemetryExtension/guest_telemetry`
* `ManagedWorkloadIdentityExtension/mwlid_extension`
Neither have a `main.version` symbol so they aren't version
stamped (upstream does the same). The generated `*.pb.go`
files that `mwlid_extension` needs already ship in
the tarball (so nothing is fetched from the network on build)
* Build the plugin manager into `_build/addon-bin/` and
rewrite the `instance_configs.cfg` file directly there
(rather than in place which keeps the unpacked source
tree pristine)
* Drop the `override_dh_systemd_enable` and
`override_dh_systemd_start` targets. With compat 12,
`dh` only runs `dh_installsystemd` so these overrides
were just dead code anyway
* Enable/start both manager units (`google-guest-agent-manager.service`
and `google-guest-compat-manager.service` via the shipped
`90-google-guest-agent.preset`) and ship the legacy
`google-guest-agent.service` and `gce-workload-cert-refresh.timer`
without enabling them
* Stamp each repo's binaries with their own upstream tags. `d/rules`
pulls in `/usr/share/dpkg/pkg-info.mk` and splits `+~`, passing
each substring to the matching `go build` (so the plugin manager
binaries no longer report the classic repo's tag in `main.version`,
and vice versa)
* Pass `-trimpath` to every plugin manager `go build` (so the
build dir doesn't get baked into the binaries)
-- Chloé 'kajiya' Smith <[email protected]> Mon, 24 Aug 2026
18:54:39 +0100
** Changed in: google-guest-agent (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2164943
Title:
[FFE] Please update to version 20260819.00
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/2164943/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
