Azure Batch Blob containers mounting issue with Ubuntu24.04 batch agent

[saikrishnaZF]

Issue Ticket

**Summary: ** We are experiencing issues with mounting multiple blob containers in an Azure Batch pool using a custom Ubuntu 24.04 image. While the configuration worked with Ubuntu 20.04, the second mount fails after upgrading to Ubuntu 24.04.

**Error Details: **

2025-03-25T12:55:11,086635880+00:00 - INFO: Setting account name, key and SAS URL for /mnt/batch/tasks/fsmounts/bfuseconnect/testdata.yaml
2025-03-25T12:55:11,089399951+00:00 - INFO: Downloading: https://packages.microsoft.com/keys/microsoft.asc as microsoft.asc
2025-03-25T12:55:11,476365351+00:00 - INFO: Downloading: https://packages.microsoft.com/config/ubuntu/24.04/prod.list as /etc/apt/sources.list.d/microsoft-prod.list
gpg: no valid OpenPGP data found.
gpg: dearmoring failed: File exists.

**Steps to Reproduce: **

1. Configure multiple blob containers in the mount configuration of the batch pool.
2. Deploy a new node with the custom Ubuntu 24.04 image.
3. Observe the first mount is successful, but the second mount fails with the error mentioned above.

**Expected Results: ** The first mount should be successful, and the second mount should also succeed without errors.

Actual Results: The first mount is successful, but the second mount fails with the error mentioned above.

**Additional Comments: ** After debugging, we identified an issue in the blobfuse mount script located at /opt/batch/bin/mount_blobfuse.sh (version 1.12.15 of the node agent). The problem appears to be caused by the following lines:

gpg --batch --no-tty -o /usr/share/keyrings/microsoft-prod.gpg --dearmor microsoft.asc

The combination of lines 162 and 163 results in microsoft.gpg being deleted while microsoft-prod.gpg is created. This causes the second mount to fail because the file already exists.

We need assistance in resolving this issue to ensure multiple blob containers can be mounted successfully on Ubuntu 24.04.

Please find the attached image.

Regards, Saikrishna

[alfpark]

Thanks for reporting this issue. This is fixed internally and is awaiting release.