terraform nomad_volume error

terraform.log

2020/11/09 17:12:15 [WARN] Provider "registry.terraform.io/hashicorp/nomad" produced an invalid plan for nomad_volume.airflow_data, but we are tolerating it because it is using the legacy plugin SDK.
    The following problems may be the cause of any confusing errors from downstream operations:
      - .deregister_on_destroy: planned value cty.True does not match config value cty.NullVal(cty.Bool)
2020/11/09 17:12:15 [TRACE] eval: *terraform.EvalCheckPlannedChange
2020/11/09 17:12:15 [TRACE] EvalCheckPlannedChange: Verifying that actual change (action Create) matches planned change (action Create)
2020/11/09 17:12:15 [TRACE] eval: *terraform.EvalGetProvider
2020/11/09 17:12:15 [TRACE] eval: *terraform.EvalReadState
2020/11/09 17:12:15 [TRACE] EvalReadState: reading state for nomad_volume.airflow_data
2020/11/09 17:12:15 [TRACE] EvalReadState: no state present for nomad_volume.airflow_data
2020/11/09 17:12:15 [TRACE] eval: *terraform.EvalReduceDiff
2020/11/09 17:12:15 [TRACE] eval: *terraform.EvalIf
2020/11/09 17:12:15 [TRACE] eval: terraform.EvalNoop
2020/11/09 17:12:15 [TRACE] eval: *terraform.EvalApplyPre
2020/11/09 17:12:15 [TRACE] eval: *terraform.EvalApply
2020/11/09 17:12:15 [DEBUG] EvalApply: ProviderMeta config value set
2020/11/09 17:12:15 [DEBUG] nomad_volume.airflow_data: applying the planned Create change
2020/11/09 17:12:15 [TRACE] GRPCProvider: ApplyResourceChange
2020/11/09 17:12:15 [DEBUG] EvalApply: ProviderMeta config value set
2020/11/09 17:12:15 [DEBUG] nomad_volume.airflow_db: applying the planned Create change
2020/11/09 17:12:15 [TRACE] GRPCProvider: ApplyResourceChange
2020-11-09T17:12:15.459-0500 [DEBUG] plugin.terraform-provider-nomad_v1.4.10_x4: 2020/11/09 17:12:15 [DEBUG] registering volume "airflow_data_pre" in namespace ""
2020-11-09T17:12:15.459-0500 [DEBUG] plugin.terraform-provider-nomad_v1.4.10_x4: 2020/11/09 17:12:15 [DEBUG] registering volume "airflow_db_pre" in namespace ""
2020-11-09T17:12:15.664-0500 [DEBUG] plugin.terraform-provider-nomad_v1.4.10_x4: 2020/11/09 17:12:15 [DEBUG] volume "airflow_data_pre" registered in namespace ""
2020-11-09T17:12:15.664-0500 [DEBUG] plugin.terraform-provider-nomad_v1.4.10_x4: 2020/11/09 17:12:15 [DEBUG] reading information for volume "airflow_data_pre" in namespace "pre-data-eng"
2020-11-09T17:12:15.715-0500 [DEBUG] plugin.terraform-provider-nomad_v1.4.10_x4: 2020/11/09 17:12:15 [DEBUG] volume "airflow_db_pre" registered in namespace ""
2020-11-09T17:12:15.715-0500 [DEBUG] plugin.terraform-provider-nomad_v1.4.10_x4: 2020/11/09 17:12:15 [DEBUG] reading information for volume "airflow_db_pre" in namespace "pre-data-eng"
2020-11-09T17:12:15.778-0500 [DEBUG] plugin.terraform-provider-nomad_v1.4.10_x4: 2020/11/09 17:12:15 [DEBUG] volume "airflow_data_pre" does not exist, so removing
2020/11/09 17:12:15 [DEBUG] nomad_volume.airflow_data: apply errored, but we're indicating that via the Error pointer rather than returning it: Provider produced inconsistent result after apply: When applying changes to nomad_volume.airflow_data, provider "registry.terraform.io/hashicorp/nomad" produced an unexpected new value: Root resource was present, but now absent.

This is a bug in the provider, which should be reported in the provider's own issue tracker.
2020/11/09 17:12:15 [TRACE] eval: *terraform.EvalMaybeTainted
2020/11/09 17:12:15 [TRACE] EvalMaybeTainted: nomad_volume.airflow_data encountered an error during creation, so it is now marked as tainted
2020/11/09 17:12:15 [TRACE] eval: *terraform.EvalWriteState
2020/11/09 17:12:15 [TRACE] EvalWriteState: removing state object for nomad_volume.airflow_data
2020/11/09 17:12:15 [TRACE] eval: *terraform.EvalApplyProvisioners
2020/11/09 17:12:15 [TRACE] EvalApplyProvisioners: nomad_volume.airflow_data has no state, so skipping provisioners
2020/11/09 17:12:15 [TRACE] eval: *terraform.EvalMaybeTainted
2020/11/09 17:12:15 [TRACE] EvalMaybeTainted: nomad_volume.airflow_data encountered an error during creation, so it is now marked as tainted
2020/11/09 17:12:15 [TRACE] eval: *terraform.EvalWriteState
2020/11/09 17:12:15 [TRACE] EvalWriteState: removing state object for nomad_volume.airflow_data
2020/11/09 17:12:15 [TRACE] eval: *terraform.EvalIf
2020/11/09 17:12:15 [TRACE] eval: *terraform.EvalIf
2020/11/09 17:12:15 [TRACE] eval: *terraform.EvalWriteDiff
2020/11/09 17:12:15 [TRACE] eval: *terraform.EvalApplyPost
2020/11/09 17:12:15 [ERROR] eval: *terraform.EvalApplyPost, err: Provider produced inconsistent result after apply: When applying changes to nomad_volume.airflow_data, provider "registry.terraform.io/hashicorp/nomad" produced an unexpected new value: Root resource was present, but now absent.

This is a bug in the provider, which should be reported in the provider's own issue tracker.
2020/11/09 17:12:15 [ERROR] eval: *terraform.EvalSequence, err: Provider produced inconsistent result after apply: When applying changes to nomad_volume.airflow_data, provider "registry.terraform.io/hashicorp/nomad" produced an unexpected new value: Root resource was present, but now absent.

This is a bug in the provider, which should be reported in the provider's own issue tracker.
2020/11/09 17:12:15 [TRACE] [walkApply] Exiting eval tree: nomad_volume.airflow_data
2020/11/09 17:12:15 [TRACE] vertex "nomad_volume.airflow_data": visit complete
2020-11-09T17:12:15.816-0500 [DEBUG] plugin.terraform-provider-nomad_v1.4.10_x4: 2020/11/09 17:12:15 [DEBUG] volume "airflow_db_pre" does not exist, so removing
2020/11/09 17:12:15 [DEBUG] nomad_volume.airflow_db: apply errored, but we're indicating that via the Error pointer rather than returning it: Provider produced inconsistent result after apply: When applying changes to nomad_volume.airflow_db, provider "registry.terraform.io/hashicorp/nomad" produced an unexpected new value: Root resource was present, but now absent.

This is a bug in the provider, which should be reported in the provider's own issue tracker.