Fix mistake setting container_count_max from wrong config parameter
authorPeter Amstutz <pamstutz@veritasgenetics.com>
Fri, 3 May 2019 15:40:43 +0000 (11:40 -0400)
committerPeter Amstutz <pamstutz@veritasgenetics.com>
Fri, 3 May 2019 15:40:43 +0000 (11:40 -0400)
refs #13996

Arvados-DCO-1.1-Signed-off-by: Peter Amstutz <pamstutz@veritasgenetics.com>

services/api/app/models/container_request.rb

index 45db4ee916f202352b658a695e0bae2184693e46..c412e4b8500c141617b18de64007078f7b715c4d 100644 (file)
@@ -217,7 +217,7 @@ class ContainerRequest < ArvadosModel
     self.mounts ||= {}
     self.secret_mounts ||= {}
     self.cwd ||= "."
-    self.container_count_max ||= Rails.configuration.Containers.MaxComputeVMs
+    self.container_count_max ||= Rails.configuration.Containers.MaxRetryAttempts
     self.scheduling_parameters ||= {}
     self.output_ttl ||= 0
     self.priority ||= 0