JES backend not honoring the `default-zones` configuration parameter

• v28
• JES backend

With the below changes to a reference.conf, I would expect my jobs to be distributed between us-central1-f and -c, but when I check the VM instances, they are all still going to us-central1-b, the cromwell default.

Do I have the default-zones in the correct location in the hierarchy? This was taken from reference.conf, but might have gotten stale in v28.

Here is a snippet of my configuration:

backend {
  default = "JES"
    providers {
              JES {
              actor-factory = "cromwell.backend.impl.jes.JesBackendLifecycleActorFactory"
 	      .... snip...
	      genomics {
			....snip....

			   # Specifies the zone(s) to use for JES jobs unless overridden by a task's runtime attributes
			   default-zones = ["us-central1-f", "us-central1-c"]
		....snip....

[LeeTL1220]

Okay, I’ll update and see if it works. Regardless, you can close this issue.

[Horneth]

@LeeTL1220 thx for the info, I will update the reference.conf