You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
We have a pipeline that allows us to test a CentOS VHD. The pipeline downloads it into a storage account and then creates an image out of it. This image is now feed into the azhpc scripts to deploy a cluster and benchmarks are run. Before December 2020 we never had a issue doing it. But now the azhpc-build fails at the install_node_setup.sh step with the message "package epel-release is not installed epel-release-7-11.noarch".
To Reproduce
Steps to reproduce the behavior:
Have a CentOS-HPC VHD at your disposal.
Download it on to a storage account and create an image out of it.
Utilize the azhpc scripts and the image to deploy a cluster.
You should encounter the error here.
Expected behavior
As before Dec 2020, the azhpc-build should be able to deploy a cluster out of the image.
Screenshots
Configuration (please complete the following information):
OS and version: CentOS 7.6 HPC (Test VHD)
Context of execution : Ubuntu from WSL2
The text was updated successfully, but these errors were encountered:
@souvik-de this is just failing as you are unable to ssh from the jumpbox to the compute instance. Have you tried to access the VMSS instance yourself (as you are able to connect to the jumpbox)? Also, does this happen consistently or just occasionally?
I cannot ssh into the headnode even after resetting with password - "Permission denied (publickey,gssapi-keyex,gssapi-with-mic) | Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password)". Happens consistently.
Describe the bug
We have a pipeline that allows us to test a CentOS VHD. The pipeline downloads it into a storage account and then creates an image out of it. This image is now feed into the azhpc scripts to deploy a cluster and benchmarks are run. Before December 2020 we never had a issue doing it. But now the azhpc-build fails at the install_node_setup.sh step with the message "package epel-release is not installed epel-release-7-11.noarch".
To Reproduce
Steps to reproduce the behavior:
Expected behavior
As before Dec 2020, the azhpc-build should be able to deploy a cluster out of the image.
Screenshots
Configuration (please complete the following information):
The text was updated successfully, but these errors were encountered: