** Description changed:

- # Impact
+ [ SRU ]
+ [ Impact ]
  
  The current azure-proxy-agent.service unit file in Ubuntu contains
  ordering directives that can cause dependency cycles during early boot
  when combined with cloud-init.service. This leads to boot instability
  and prevents successful verification in Azure VMs.
  
  This fix adjusts the service definition to:
  
  - Start the agent only after local filesystems are ready, ensuring 
logs/config paths are accessible.
  - Run before networking is configured (Before=network-pre.target) so the 
agent is present when Azure expects it.
  - Avoid pulling in network targets by itself (removing 
Wants=network-pre.target) to prevent conflicts with cloud-init.
  - Add clean shutdown handling (Before=shutdown.target, 
Conflicts=shutdown.target).
  
  Together, these changes eliminate the ordering cycle and ensure both the
  Azure agent and cloud-init run reliably.
  
+ [ Test Plan ]
+ 
+  * As described in this SRU exception:
+ https://documentation.ubuntu.com/sru/en/latest/reference/exception-
+ Azure-Proxy-Agent-Updates. The agent will be installed on a live image
+ (before first boot) and CPC will run their test suites on Azure to
+ verify that the VM behaves as expected and that no regression is
+ introduced.
+ 
+  * The Microsoft team responsible for this agent will also use their own
+ tests to verify the new version.
+ 
+ * In addition, we conduct the following specific checks for this fix:
+     Build and install the updated azure-proxy-agent package.
+ 
+     Launch an Azure VM using a custom image with the updated package.
+ 
+     Verify:
+ 
+       - The VM boots cleanly.
+       - The VM is fully reachable via SSH.
+       - The azure-proxy-agent.service starts successfully before networking.
+       - cloud-init.service completes as expected.
+ 
+     Successful boot and SSH accessibility demonstrate that the cycle is
+ resolved and normal provisioning is restored.
+ 
+ [ Where problems could occur ]
+ 
+ There is a low risk of regressions as changes only affect the unit file
+ ordering and shutdown behavior:
+ 
+ If misordered, the agent may start too early/late, which would show up
+ immediately in boot logs.
+ 
+ 
+ [ Original Description ]
+ # Impact
+ 
+ The current azure-proxy-agent.service unit file in Ubuntu contains
+ ordering directives that can cause dependency cycles during early boot
+ when combined with cloud-init.service. This leads to boot instability
+ and prevents successful verification in Azure VMs.
+ 
+ This fix adjusts the service definition to:
+ 
+ - Start the agent only after local filesystems are ready, ensuring 
logs/config paths are accessible.
+ - Run before networking is configured (Before=network-pre.target) so the 
agent is present when Azure expects it.
+ - Avoid pulling in network targets by itself (removing 
Wants=network-pre.target) to prevent conflicts with cloud-init.
+ - Add clean shutdown handling (Before=shutdown.target, 
Conflicts=shutdown.target).
+ 
+ Together, these changes eliminate the ordering cycle and ensure both the
+ Azure agent and cloud-init run reliably.
+ 
  # Test Case
  
  Build and install the updated azure-proxy-agent package.
  
  Launch an Azure VM using a custom image with the updated package.
  
  Verify:
  
  - The VM boots cleanly.
  - The VM is fully reachable via SSH.
  - The azure-proxy-agent.service starts successfully before networking.
  - cloud-init.service completes as expected.
  
- 
- Successful boot and SSH accessibility demonstrate that the cycle is resolved 
and normal provisioning is restored.
+ Successful boot and SSH accessibility demonstrate that the cycle is
+ resolved and normal provisioning is restored.
  
  # Regression Potential
  
  Low. The changes only affect the unit file ordering and shutdown
  behavior:
  
  If misordered, the agent may start too early/late, which would show up
  immediately in boot logs.
  
  The updated ordering has been validated in Azure VMs and matches the
  intended design of network-pre.target and cloud-init:
  
- 
  ❯ az vm create --resource-group miriam-azure-proxy --name 
t-m-questing-amd64-server-systemd --image 
"/subscriptions/4d55f386-4e21-46d0-9a72-4fef530d717a/resourceGroups/miriam-azure-proxy/providers/Microsoft.Compute/galleries/agent/images/questing-server-amd64-gen2"
 --ssh-key-values ~/.ssh/id_rsa.pub --size Standard_D2s_v3 --admin-username 
ubuntu
  The default value of '--size' will be changed to 'Standard_D2s_v5' from 
'Standard_DS1_v2' in a future release.
- Selecting "uksouth" may reduce your costs. The region you've selected may 
cost more for the same services. You can disable this message in the future 
with the command "az config set core.display_region_identified=false". Learn 
more at Windows help and learning  
+ Selecting "uksouth" may reduce your costs. The region you've selected may 
cost more for the same services. You can disable this message in the future 
with the command "az config set core.display_region_identified=false". Learn 
more at Windows help and learning
  
  ResourceGroup       PowerState    PublicIpAddress    Fqdns
  PrivateIpAddress    MacAddress         Location
  
  miriam-azure-proxy  VM running    74.234.208.235              10.0.0.4        
    7C-ED-8D-8F-46-02  westeurope
  ❯ ssh [email protected]
  The authenticity of host '74.234.208.235 (74.234.208.235)' can't be 
established.
  ED25519 key fingerprint is SHA256:AV+fjV8N2feJfoSP+0qBPkIEO8vzGN+5HfO1N3YyeX4.
  This key is not known by any other names.
  Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
  Warning: Permanently added '74.234.208.235' (ED25519) to the list of known 
hosts.
  Welcome to Ubuntu Questing Quokka (development branch) (GNU/Linux 
6.17.0-1003-azure x86_64)
  
  Documentation:  Ubuntu documentation
  
  Management:     https://landscape.canonical.com
  
  Support:        Ubuntu Pro | Ubuntu
  
-  System information as of Mon Sep 29 12:45:27 UTC 2025
- 
-   System load:  0.95              Processes:             127
-   Usage of /:   6.2% of 27.95GB   Users logged in:       0
-   Memory usage: 4%                IPv4 address for eth0: 10.0.0.4
-   Swap usage:   0%
+  System information as of Mon Sep 29 12:45:27 UTC 2025
+ 
+   System load:  0.95              Processes:             127
+   Usage of /:   6.2% of 27.95GB   Users logged in:       0
+   Memory usage: 4%                IPv4 address for eth0: 10.0.0.4
+   Swap usage:   0%
  
  0 updates can be applied immediately.
  
  The programs included with the Ubuntu system are free software;
  the exact distribution terms for each program are described in the
  individual files in /usr/share/doc/*/copyright.
  
  Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by
  applicable law.
  
  ubuntu@t-m-questing-amd64-server-systemd:~$ dpkg -l azure-proxy-agent
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name              Version         Architecture Description
  
+++-=================-===============-============-=================================
  ii  azure-proxy-agent 1.0.30-0ubuntu6 amd64        Azure Guest Proxy Agent
  ubuntu@t-m-questing-amd64-server-systemd:~$ systemctl --failed --no-legend
  ubuntu@t-m-questing-amd64-server-systemd:~$ systemctl is-active 
azure-proxy-agent
  active
  ubuntu@t-m-questing-amd64-server-systemd:~$ systemctl status azure-proxy-agent
  ● azure-proxy-agent.service - Microsoft Azure GuestProxyAgent
-      Loaded: loaded (/usr/lib/systemd/system/azure-proxy-agent.service; 
enabled; preset: enabled)
-      Active: active (running) since Mon 2025-09-29 12:44:12 UTC; 2min 3s ago
-  Invocation: 2da12dcbef524fa8a617e7c27d5f4fc8
-        Docs: man:azure-proxy-agent(8)
-    Main PID: 452 (azure-proxy-age)
-       Tasks: 5 (limit: 9505)
-      Memory: 32.7M (peak: 49.7M)
-         CPU: 196ms
-      CGroup: /system.slice/azure-proxy-agent.service
-              └─452 /usr/sbin/azure-proxy-agent
+      Loaded: loaded (/usr/lib/systemd/system/azure-proxy-agent.service; 
enabled; preset: enabled)
+      Active: active (running) since Mon 2025-09-29 12:44:12 UTC; 2min 3s ago
+  Invocation: 2da12dcbef524fa8a617e7c27d5f4fc8
+        Docs: man:azure-proxy-agent(8)
+    Main PID: 452 (azure-proxy-age)
+       Tasks: 5 (limit: 9505)
+      Memory: 32.7M (peak: 49.7M)
+         CPU: 196ms
+      CGroup: /system.slice/azure-proxy-agent.service
+              └─452 /usr/sbin/azure-proxy-agent
  
  Sep 29 12:44:12 ubuntu azure-proxy-agent[452]: ============== GuestProxyAgent 
(1.0.30) is starting on Linux:Ubuntu-25.10.0(>
  Sep 29 12:44:12 ubuntu azure-proxy-agent[452]: Start proxy listener at 
'127.0.0.1:3080'.
  Sep 29 12:44:12 ubuntu azure-proxy-agent[452]: Success loaded bpf object.
  Sep 29 12:44:12 ubuntu azure-proxy-agent[452]: Success updated bpf 
skip_process map with pid=452.
  Sep 29 12:44:12 ubuntu azure-proxy-agent[452]: Success updated bpf map for 
WireServer support.
  Sep 29 12:44:12 ubuntu azure-proxy-agent[452]: Success updated bpf map for 
IMDS support.
  Sep 29 12:44:12 ubuntu azure-proxy-agent[452]: Success updated bpf map for 
Host GAPlugin support.
  Sep 29 12:44:12 ubuntu azure-proxy-agent[452]: Success attached bpf prog.
  Sep 29 12:44:22 ubuntu azure-proxy-agent[452]: 
{"id":1,"method":"GET","url":"/metadata/instance?api-version=2021-08-01&exte>
  Sep 29 12:44:22 ubuntu azure-proxy-agent[452]: telemetry event reader task 
started.
  
- ubuntu@t-m-questing-amd64-server-systemd:~$ journalctl | grep cloud-init 
+ ubuntu@t-m-questing-amd64-server-systemd:~$ journalctl | grep cloud-init
  Sep 29 12:44:04 ubuntu systemd[1]: Starting cloud-init-main.service - 
Cloud-init: Single Process...
  Sep 29 12:44:18 ubuntu systemd[1]: Started cloud-init-main.service - 
Cloud-init: Single Process.
  Sep 29 12:44:18 ubuntu systemd[1]: Starting cloud-init-local.service - 
Cloud-init: Local Stage (pre-network)...
  Sep 29 12:44:19 ubuntu cloud-init[677]: Cloud-init v. 
25.3~2g890873f5-0ubuntu2 running 'init-local' at Mon, 29 Sep 2025 12:44:19 
+0000. Up 30.23 seconds.
  Sep 29 12:44:22 ubuntu azure-proxy-agent[452]: 
{"id":1,"method":"GET","url":"/metadata/instance?api-version=2021-08-01&extended=true","clientIp":"127.0.0.1","clientPort":48264,"ip":"169.254.169.254","port":80,"userId":0,"userName":"root","userGroups":["root"],"processFullPath":"/usr/bin/python3.13","processCmdLine":"/usr/bin/python3
 /usr/bin/cloud-init --all-stages","runAsElevated":true,"responseStatus":"200 
OK","elapsedTime":81,"errorDetails":""}
  Sep 29 12:44:24 t-m-questing-amd64-server-systemd systemd[1]: Reload 
requested from client PID 743 ('systemctl') (unit cloud-init-main.service)...
  Sep 29 12:44:24 t-m-questing-amd64-server-systemd systemd[1]: Finished 
cloud-init-local.service - Cloud-init: Local Stage (pre-network).
  Sep 29 12:44:25 t-m-questing-amd64-server-systemd systemd[1]: Starting 
cloud-init-network.service - Cloud-init: Network Stage...
  Sep 29 12:44:25 t-m-questing-amd64-server-systemd cloud-init[677]: Cloud-init 
v. 25.3~2g890873f5-0ubuntu2 running 'init' at Mon, 29 Sep 2025 12:44:25 +0000. 
Up 36.25 seconds.
  Sep 29 12:44:25 t-m-questing-amd64-server-systemd cloud-init[677]: ci-info: 
+++++++++++++++++++++++++++Net device info++++++++++++++++++++++++++++
  Sep 29 12:44:25 t-m-questing-amd64-server-systemd cloud-init[677]: ci-info: 
+--------+-------+-----------+-----------+-------+-------------------+
  Sep 29 12:44:25 t-m-questing-amd64-server-systemd cloud-init[677]: ci-info: | 
Device |   Up  |  Address  |    Mask   | Scope |     Hw-Address    |
  Sep 29 12:44:25 t-m-questing-amd64-server-systemd cloud-init[677]: ci-info: 
+--------+-------+-----------+-----------+-------+-------------------+
  Sep 29 12:44:25 t-m-questing-amd64-server-systemd cloud-init[677]: ci-info: | 
 eth0  | False |     .     |     .     |   .   | 7c:ed:8d:8f:46:02 |
  Sep 29 12:44:25 t-m-questing-amd64-server-systemd cloud-init[677]: ci-info: | 
  lo   |  True | 127.0.0.1 | 255.0.0.0 |  host |         .         |
  Sep 29 12:44:25 t-m-questing-amd64-server-systemd cloud-init[677]: ci-info: | 
  lo   |  True |  ::1/128  |     .     |  host |         .         |
  Sep 29 12:44:25 t-m-questing-amd64-server-systemd cloud-init[677]: ci-info: 
+--------+-------+-----------+-----------+-------+-------------------+
  Sep 29 12:44:25 t-m-questing-amd64-server-systemd cloud-init[677]: ci-info: 
+++++++++++++++++++Route IPv6 info+++++++++++++++++++
  Sep 29 12:44:25 t-m-questing-amd64-server-systemd cloud-init[677]: ci-info: 
+-------+-------------+---------+-----------+-------+
  Sep 29 12:44:25 t-m-questing-amd64-server-systemd cloud-init[677]: ci-info: | 
Route | Destination | Gateway | Interface | Flags |
  Sep 29 12:44:25 t-m-questing-amd64-server-systemd cloud-init[677]: ci-info: 
+-------+-------------+---------+-----------+-------+
  Sep 29 12:44:25 t-m-questing-amd64-server-systemd cloud-init[677]: ci-info: 
+-------+-------------+---------+-----------+-------+
  Sep 29 12:44:33 t-m-questing-amd64-server-systemd systemd[1]: Reload 
requested from client PID 1005 ('systemctl') (unit cloud-init-main.service)...
  Sep 29 12:44:35 t-m-questing-amd64-server-systemd systemd[1]: Finished 
cloud-init-network.service - Cloud-init: Network Stage.
  Sep 29 12:44:35 t-m-questing-amd64-server-systemd systemd[1]: Listening on 
cloud-init-hotplugd.socket - cloud-init hotplug hook socket.
  Sep 29 12:44:35 t-m-questing-amd64-server-systemd cloud-init[677]: Cloud-init 
v. 25.3~2g890873f5-0ubuntu2 running 'modules:config' at Mon, 29 Sep 2025 
12:44:35 +0000. Up 46.87 seconds.
  Sep 29 12:44:39 t-m-questing-amd64-server-systemd python3[1089]: 
2025-09-29T12:44:39.524242Z INFO Daemon Daemon cloud-init is enabled: True
  Sep 29 12:44:39 t-m-questing-amd64-server-systemd python3[1089]: 
2025-09-29T12:44:39.526915Z INFO Daemon Daemon Using cloud-init for provisioning
  Sep 29 12:44:42 t-m-questing-amd64-server-systemd cloud-init[677]: Cloud-init 
v. 25.3~2g890873f5-0ubuntu2 running 'modules:final' at Mon, 29 Sep 2025 
12:44:42 +0000. Up 53.83 seconds.
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[1578]: 
#############################################################
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[1579]: 
-----BEGIN SSH HOST KEY FINGERPRINTS-----
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[1581]: 256 
SHA256:DaPtOsltcZrErCrmsHEMsZS3AxNFSMQ5ycVEHp9iGRM 
root@t-m-questing-amd64-server-systemd (ECDSA)
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[1583]: 256 
SHA256:AV+fjV8N2feJfoSP+0qBPkIEO8vzGN+5HfO1N3YyeX4 
root@t-m-questing-amd64-server-systemd (ED25519)
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[1587]: 3072 
SHA256:Enlzy1vNQzB+oAElwsUuSEnJnUWBmf+N6EJJ8VR07lM 
root@t-m-questing-amd64-server-systemd (RSA)
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[1588]: -----END 
SSH HOST KEY FINGERPRINTS-----
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[1589]: 
#############################################################
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: Cloud-init 
v. 25.3~2g890873f5-0ubuntu2 finished at Mon, 29 Sep 2025 12:44:43 +0000. 
Datasource DataSourceAzure [seed=/dev/sr0].  Up 54.36 seconds
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: Generating 
public/private rsa key pair.
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: Your 
identification has been saved in /etc/ssh/ssh_host_rsa_key
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: Your 
public key has been saved in /etc/ssh/ssh_host_rsa_key.pub
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: The key 
fingerprint is:
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: 
SHA256:Enlzy1vNQzB+oAElwsUuSEnJnUWBmf+N6EJJ8VR07lM 
root@t-m-questing-amd64-server-systemd
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: The key's 
randomart image is:
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: +---[RSA 
3072]----+
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: |   
o.=.XB*= =    |
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: |    = 
Ooo. * +   |
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: |   . .o*o 
o o E  |
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: |    . 
oo++ o *   |
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: |     
..oSooo+ +  |
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: |      o.. 
oo.. . |
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: |     . .  
.      |
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: |      . . 
       |
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: |       .  
       |
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: 
+----[SHA256]-----+
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: Generating 
public/private ecdsa key pair.
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: Your 
identification has been saved in /etc/ssh/ssh_host_ecdsa_key
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: Your 
public key has been saved in /etc/ssh/ssh_host_ecdsa_key.pub
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: The key 
fingerprint is:
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: 
SHA256:DaPtOsltcZrErCrmsHEMsZS3AxNFSMQ5ycVEHp9iGRM 
root@t-m-questing-amd64-server-systemd
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: The key's 
randomart image is:
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: +---[ECDSA 
256]---+
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: |=+@E.     
       |
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: | B+.* .   
       |
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: |.=.* o  o 
       |
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: |.o= o  o 
+       |
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: |o  o  .oS 
.      |
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: | o  .  .= 
.      |
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: |o o  . 
=.=       |
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: | =o   =.= 
       |
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: |.o.....o  
       |
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: 
+----[SHA256]-----+
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: Generating 
public/private ed25519 key pair.
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: Your 
identification has been saved in /etc/ssh/ssh_host_ed25519_key
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: Your 
public key has been saved in /etc/ssh/ssh_host_ed25519_key.pub
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: The key 
fingerprint is:
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: 
SHA256:AV+fjV8N2feJfoSP+0qBPkIEO8vzGN+5HfO1N3YyeX4 
root@t-m-questing-amd64-server-systemd
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: The key's 
randomart image is:
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: 
+--[ED25519 256]--+
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: |      ..  
.   .o |
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: |       
oo. . +..+|
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: |       
oo.  + + *|
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: |      . 
+.  .+ +.|
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: |       
=S. ...=  |
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: |        B 
o .o.o |
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: |       . 
+ = +o..|
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: |          
. =.BoE|
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: |          
 . o+O*|
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd cloud-init[677]: 
+----[SHA256]-----+
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd systemd[1]: 
cloud-init-main.service: Deactivated successfully.
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd systemd[1]: 
cloud-init-main.service: Consumed 2.261s CPU time, 79.8M memory peak.
  Sep 29 12:44:43 t-m-questing-amd64-server-systemd systemd[1]: Reached target 
cloud-init.target - Cloud-init target.
  
- 
  #Other Info
  
  Last bug related: 
https://bugs.launchpad.net/ubuntu/+source/azure-proxy-agent/+bug/2122345
  Discussion on the upstream issue can be found here: Add 
`DefaultDependencies=no` back for Linux GPA service : 
https://github.com/Azure/GuestProxyAgent/pull/272#discussion_r2370319319

** Changed in: azure-proxy-agent (Ubuntu Plucky)
       Status: New => In Progress

-- 
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:
  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

Reply via email to