OpenSSH not installed on Azure Worker

[benoit.rey]

Hello,

I’ve been experiencing an issue with my V365 backup copy jobs to Azure.

The workers were successfully created on the Azure side, but they get stuck at the OpenSSH installation step, ending with a timeout and then deleting the worker.

[21.10.2024 09:08:29.007] 131 (936) New virtual machine is created (IP: 4.233.108.196, name: VBO-Worker-62efd0bfa1ab4198b5e54c38f12b2057)
[21.10.2024 09:08:29.007] 131 (936) Installing OpenSSH server...
[21.10.2024 09:10:59.855] 131 (936) Waiting for SSH service...
[21.10.2024 09:10:59.855] 131 (936) Waiting for: 4.233.108.196:22...
[21.10.2024 09:11:20.871] 210 (4128) Waiting time: 00:00:21.0110416, A connection attempt failed because the connected party did not respond within a certain period, or an established connection failed because the host did not respond 4.233.108.196:22
[21.10.2024 09:26:06.134] 131 (936) SSH service is not available at: 4.233.108.196:22.
[21.10.2024 09:26:06.134] 131 (936) Deleting a virtual machine: VBO-Worker-62efd0bfa1ab4198b5e54c38f12b2057...

It's not a Azure firewall issue because we ran a netstat -a to check if the worker was listening on TCP port 22 (it's not listening on this port) and normally the installation is logged successfully after the connection

For example :
[15.09.2024 09:01:38.275] 121 (5664) Installing OpenSSH server...
[15.09.2024 09:04:09.327] 121 (5664) Waiting for SSH service...
[15.09.2024 09:04:09.327] 121 (5664) Waiting for: 4.212.91.105:22...
[15.09.2024 09:04:09.358] 219 (2972) Connection is available, elapsed time: 00:00:00.0213942
[15.09.2024 09:04:09.358] 121 (5664) OpenSSH server installed

At the end of the backup copy job, the other worker was stuck at installing OpenSSH but it was still seen as "created" so it deleted the former worker which lead to this issue (now, I have no worker on Azure side)

I have raised a ticket to Veeam Support : 03208115 but they still haven't replied. Has someone encountered this issue and found a solution ?

Regards

[Polina]

Hi benoit.rey,

Please stay in touch with support, I'll escalate your case to RnD. The issue is most likely due to the latest updates to either the OS or OpenSSH. We are already working on a solution.