Hi,
We are going to try to reproduce this issue and will update you asap
Hi SmugTurtle78 , can you share you configuration? (without the secrets)
- are you working vpc? did you try configure only one of the params?
We are working vpc, actually I didn't try on of the params cause we need them both...
Do you mean to the resources configuration or the general?
resources configuration, so you have subnet ID and the security group ID and it failed with it?
[{"resource_name": "clearml_agent_gpu", "instance_type": "g4dn.xlarge", "cpu_only": false, "is_spot": false, "availability_zone": "eu-west-1a", "ami_id": "ami-00511f188b842c5cc", "num_instances": 1, "queue_name": "default", "tags": "*", "ebs_device_name": "/dev/sda1", "ebs_volume_size": 500, "ebs_volume_type": "gp3", "key_name": "***", "security_group_ids": "", "subnet_id": "**"}]
thanks SmugTurtle78 , checking it
Hi TimelyPenguin76 , how are you? have you found something?
yes, this fix almost done testing and will be part of the next release, will keep you updated about it
Hi TimelyPenguin76 , What is your estimation to the next release ? We are really waiting for this 🙂
SmugTurtle78
by the end of this week
Hi TimelyPenguin76 , Is there any news about the release? 🙂