Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escaping: Escape characters +-&|!(){}[]^"~*?:\ with \, e.g. \+
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Answered
Hi, I Am Getting This Error When Using The Aws Auto_Scaler Service (With The Pro Version):

Hi,
I am getting this error when using the aws auto_scaler service (with the PRO version):
Traceback (most recent call last): File "/root/.clearml/venvs-builds/3/task_repository/clearml-apps.git/apps/auto_scaler/auto_scaler.py", line 320, in supervisor instance_id = self.driver.spin_up_worker(resource_conf, worker_prefix, queue, task_id=task_id) File "/root/.clearml/venvs-builds/3/task_repository/clearml-apps.git/apps/auto_scaler/cloud_driver.py", line 151, in spin_up_worker instance_id = self._spin_up_worker(resource_conf, worker_prefix, queue_name, task_id) File "/root/.clearml/venvs-builds/3/task_repository/clearml-apps.git/apps/auto_scaler/aws_driver.py", line 154, in _spin_up_worker instances = ec2.run_instances(**launch_specification) File "/root/venv/lib/python3.8/site-packages/botocore/client.py", line 508, in _api_call return self._make_api_call(operation_name, kwargs) File "/root/venv/lib/python3.8/site-packages/botocore/client.py", line 911, in _make_api_call raise error_class(parsed_response, operation_name) botocore.exceptions.ClientError: An error occurred (InvalidParameterCombination) when calling the RunInstances operation: Network interfaces and an instance-level security groups may not be specified on the same requestDid anyone know why? ( I had specified the subnet ID and the security group ID as requested on the UI)
Also read https://github.com/saltstack/salt/issues/25569 and I think that maybe there is a bug with the current implementation...

  
  
Posted 2 years ago
Votes Newest

Answers 12


Hi,
We are going to try to reproduce this issue and will update you asap

  
  
Posted 2 years ago

Hi TimelyPenguin76 , What is your estimation to the next release ? We are really waiting for this 🙂

  
  
Posted 2 years ago

SmugTurtle78
by the end of this week

  
  
Posted 2 years ago

thanks SmugTurtle78 , checking it

  
  
Posted 2 years ago

yes, this fix almost done testing and will be part of the next release, will keep you updated about it

  
  
Posted 2 years ago

Hi SmugTurtle78 , can you share you configuration? (without the secrets)

  • are you working vpc? did you try configure only one of the params?
  
  
Posted 2 years ago

Hi TimelyPenguin76 , Is there any news about the release? 🙂

  
  
Posted 2 years ago

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?

  
  
Posted 2 years ago

Hi TimelyPenguin76 , how are you? have you found something?

  
  
Posted 2 years ago

resources configuration, so you have subnet ID and the security group ID and it failed with it?

  
  
Posted 2 years ago

Yes 🙂

  
  
Posted 2 years ago

[{"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": "**"}]

  
  
Posted 2 years ago
1K Views
12 Answers
2 years ago
one year ago
Tags
aws
Similar posts