You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a terraform environment that creates a VM, add nomad to the VM and then deploys a number of nomad jobs to the environment - this has been working for about 18months.
A recent change to the terraform-nomad-provider (1.4 is broke, 1.3 works) has changed this so that when running terraform plan or terraform apply that it seems to fail in building the "environment". No state file is built and there is no prompt for whether to make changes.
The text was updated successfully, but these errors were encountered:
nhi-vanye
changed the title
nomad 0.3 to 0.4 all jobs are failing - not even prompting for confirmation
nomad 1.3 to 1.4 all jobs are failing - not even prompting for confirmation
May 27, 2019
I have a terraform environment that creates a VM, add nomad to the VM and then deploys a number of nomad jobs to the environment - this has been working for about 18months.
A recent change to the terraform-nomad-provider (1.4 is broke, 1.3 works) has changed this so that when running
terraform plan
orterraform apply
that it seems to fail in building the "environment". No state file is built and there is no prompt for whether to make changes.A typical error looks like
The
192.168.19.100
is avsphere_virtual_machine
resource that has not yes been created (it should be as part of the apply)Terraform Version
I have narrowed it down to a nomad 1.4 issue - fixing the plugin to use
version ~> 1.3.0
worked.Looked through the change log for 1.4 and nothing seemed to jump out ( did try setting detach to false - no change in behavior).
A typical job file looks like
The text was updated successfully, but these errors were encountered: