Dimitar Velinov

Deployment can also fail during VMs creation. ``` Task 103307 | 13:23:33 | Creating missing vms: diego-cell/55943a69-942c-4000-9dd4-8c4d90dc2259 (0) (00:13:23) L Error: Timed out pinging VM 'i-01cf8571465adb6ff' with agent '82392b52-cdfe-4fd6-979b-ae146f24f246' after...

Find attached bosh-agent.log + syslog from a failing VM. [bosh_agent_log_1.txt](https://github.com/user-attachments/files/22091463/bosh_agent_log_1.txt) [bosh_agent_log.txt](https://github.com/user-attachments/files/22091462/bosh_agent_log.txt) [bosh_syslog.txt](https://github.com/user-attachments/files/22091464/bosh_syslog.txt)

Compilation VM type used on AWS is c5a.xlarge.

Find attached the cloud-config for both BBL environments. [bosh-cloud-config-AWS.txt](https://github.com/user-attachments/files/22113553/bosh-cloud-config-AWS.txt) [bosh-cloud-config-GCP.txt](https://github.com/user-attachments/files/22113554/bosh-cloud-config-GCP.txt)

Investigating together with @ramonskie we managed to find the agent is restarting: ``` 2025-09-03T09:39:41.317269+00:00 7cef1b80-dfd9-4ec2-bd24-8de90ce45118 bosh-agent[573]: ******************** 2025-09-03T09:39:41.317307+00:00 7cef1b80-dfd9-4ec2-bd24-8de90ce45118 bosh-agent[573]: [Cmd Runner] 2025/09/03 09:39:41 DEBUG - Running command 'ip r'...

We have configured using c5.2xlarge as the vm type. ``` root@a6b9e08df9c7:/home/bbl/bbl-state# vim bosh-cc.yml root@a6b9e08df9c7:/home/bbl/bbl-state# bosh ucc bosh-cc.yml Using environment 'https://10.0.0.6:25555' as client 'admin' vm_types: - name: c5a.xlarge cloud_properties: - instance_type:...

[Garden runc 1.71.0](https://github.com/cloudfoundry/garden-runc-release/releases/tag/v1.71.0) is out and Noble validation pipeline is fully green now without any manual support. Thanks for the collaboration colleagues!