Azure / cyclecloud-slurm

Azure CycleCloud project to enable users to create, configure, and use Slurm HPC clusters.
MIT License
56 stars 43 forks source link

Parameter UsePublicNet is not recognized #253

Open gevaertw opened 4 months ago

gevaertw commented 4 months ago

Since this week, when importing this project in my CycleCloud deployment I have the error "Parameter UsePublicNet is not recognized" when trying to deploy the template as - is (the goal is to update it but the error is in the as-is template as well)

The below method worked well just a few weeks ago when I last used it...

to reproduce: log on to the cyclecloud server, with the cyclecloud cli installed on it run these commands:

PROJECTNAME=MyProject
LOCKER=$(cyclecloud locker list | cut -d' ' -f1)  
cyclecloud project init $PROJECTNAME
cd $PROJECTNAME
cyclecloud project default_locker $LOCKER --global
cyclecloud project fetch https://github.com/Azure/cyclecloud-slurm ./
cyclecloud import_template --force -f ./templates/slurm.txt
cyclecloud project upload

In cyclecloud create a new cluster from the new template

when I try to save the template I get the error "Parameter UsePublicNet is not recognized"

This parameter is not available in the ./templates/slurm.txt file, nor does it seem to appear in any of the other files downloaded using the project fetch command...

ActivityId  #665f22c0-0071-5a84c5cc406e-0    
Category    system   
ClusterName 01   
EntryPoint  https://10.16.0.5/exec/form/Create:Cloud.Cluster     
Id  #665f22c0-0091-5a84c5cc406e-0    
Level   
Warning
warning

Message Parameter UsePublicNet is not known (referenced by node scheduler, attribute NetworkInterfaces[0].AssociatePublicIpAddress)  
Module  application.template.util    
OperationId #665f22c0-0081-5a84c5cc406e-0    
Primary true     
Priority    medium   
Time    2:20 PM  
User    cycleadmin

its not possible to save the cluster with the error...

gevaertw commented 4 months ago

Possibly this is related to the used Slurm version.. I'm on 23.02.7-1 now and it works, but I believe that when I had the issue, I was on a later Slurm version.