This bug was fixed in the package azure-proxy-agent -
1.0.30-0ubuntu6~25.04.1
---------------
azure-proxy-agent (1.0.30-0ubuntu6~25.04.1) plucky; urgency=medium
[ Daniel Draper ]
* d/p/fix-systemd-deps-cycle.patch: ensure the service is terminated on
system shutdown (LP: #2125930)
azure-proxy-agent (1.0.30-0ubuntu4~25.04.2) plucky; urgency=medium
* d/p/fix-systemd-deps-cycle.patch: fix dependency cycle in the unit file.
Use DefaultDependencies=no to remove the dependency on basic.target
(LP: #2122345)
azure-proxy-agent (1.0.30-0ubuntu4~25.04.1) plucky; urgency=medium
* Backport to plucky (LP: #2115197), with the following changes:
- d/proxy-agent.json, d/t/smoke: re-enable logging to file. The
modification of the logging behaviour was not preceded by adequate prior
communication to potential users of the agent regarding the intended
change and its consequences.
azure-proxy-agent (1.0.30-0ubuntu4) questing; urgency=medium
* d/t/control: add the isolation-machine restriction to the smoke test, as
the agent needs a VM.
azure-proxy-agent (1.0.30-0ubuntu3) questing; urgency=medium
* d/p/cargo-vendor-workspace-ignore.patch: add missing DEP-3 header
* d/p/systemd-service-description.patch: add missing DEP-3 header
azure-proxy-agent (1.0.30-0ubuntu2) questing; urgency=medium
* Fix failing autopkgtest.
Since we stopped logging to a file, the smoke test was failing. We can
simply read the logs from the journal instead to fix the issue.
(LP: #2112315)
* Remove deprecated lintian-overrides.
The systemd service file was modified upstream and some of the
lintian-overrides are not needed anymore.
* Include Cargo.lock in the binary package.
The MIR doc for rust packages states that the Cargo.lock should be
included in the package.
azure-proxy-agent (1.0.30-0ubuntu1) questing; urgency=medium
* New upstream version 1.0.30.
* d/rules: use the main Cargo.toml to create the vendor directory.
* debian: create README.source and add script to update crates.
This is necessary in case a vulnerability is found in one of the
dependencies and the package needs to be rebuilt.
* d/p/systemd-service-description.patch: refresh patch.
The patch was not applying correctly on top of the new upstream version.
* d/copyright: remove superfuous patterns as some dependencies were removed.
* Update XS-Vendored-Sources-Rust and verify it during build.
This also included adding a patch to exclude the rust-vendor directory
from the workspace.
* d/control: change Section to admin.
The Section is not about the programing language used to write the
software but should reflect what the package is used for.
* Generate new vendor directory
* Disable logging to file. The new version of the agent supports disabling
logging to files by configuring the log directory to an empty string. This
way, only the logs are only going to the journal and don't fill the disk.
-- Miriam España Acebal <[email protected]> Tue, 30 Sep 2025
12:18:00 +0200
** Changed in: azure-proxy-agent (Ubuntu Plucky)
Status: Fix Committed => 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/2125930
Title:
[SRU] azure-proxy-agent: fix service file ordering to avoid cycle with
cloud-init
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/azure-proxy-agent/+bug/2125930/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
