A Microsoft tool for creating, managing, operating, and optimizing high-performance computing (HPC) and big compute clusters in Azure.
Hello @TA齊藤 隆之(アンクル)(Saito Takayuki)_SCC ,
The symptom raises the suspicion over the path to the blob file being blocked (failed to download response and write to file).
- Could you please manually login to the RHEL VM and try nslookup for that storage blob hostname ?
sample command:
Additionally, it'll be good to test the same manually using curl command to see if it works now (because while installation it throws EOF error)nslookup <storage-account>.blob.core.windows.net
sample command:curl -v -L "https://<storage-acconut>.blob.core.windows.net/cyclecloud/cache/jetpack/8.7.1/jetpack-8.7.1-linux.tar.gz?{SAS-if-any}" -o /tmp/jetpack.tgz
As a work-around, you can install Jetpack via YUM so the node doesn’t need to pull files from your storage blob.
Sample yaml file which can help to install via cloud-init:
sudo tee /etc/yum.repos.d/cyclecloud.repo <<'EOF'
[cyclecloud]
name=cyclecloud
baseurl=https://packages.microsoft.com/yumrepos/cyclecloud
gpgcheck=1
gpgkey=https://packages.microsoft.com/keys/microsoft.asc
EOF
sudo yum install -y jetpack8
#run jetpack init if needed
Note: This path uses packages.microsoft.com, bypassing your Storage account entirely for the Jetpack payload. (reference: https://learn.microsoft.com/en-us/azure/cyclecloud/how-to/install-jetpack?view=cyclecloud-8#install-jetpack-with-yum-or-apt)
If you’re in an office/organisation network, ensure outbound to packages.microsoft.com:443 is allowed.