consul template invalid memory address or nil pointer dereference" after vault is sealed

[fredwangwang]

Nomad version

1.0.4

Issue

     2021/07/12 21:17:44.900371 [INFO] (runner) creating watcher
     2021/07/12 21:17:44.900610 [INFO] (runner) starting
 panic: runtime error: invalid memory address or nil pointer dereference
 [signal SIGSEGV: segmentation violation code=0x1 addr=0x30 pc=0x18ce785]
 goroutine 928 [running]:
 github.com/hashicorp/consul-template/dependency.isKVv2(0xc002c56770, 0xc002a57712, 0x28, 0x0, 0x0, 0xc000148d00, 0x0, 0x0)
         github.com/hashicorp/consul-template@v0.25.1/dependency/vault_common.go:305 +0x365
 github.com/hashicorp/consul-template/dependency.(*VaultReadQuery).readSecret(0xc004c67090, 0xc003704750, 0xc004c67270, 0x2, 0x203001, 0x203001)
         github.com/hashicorp/consul-template@v0.25.1/dependency/vault_read.go:142 +0x3fa
 github.com/hashicorp/consul-template/dependency.(*VaultReadQuery).fetchSecret(0xc004c67090, 0xc003704750, 0xc004c67220, 0xc004c67220, 0x0)
         github.com/hashicorp/consul-template@v0.25.1/dependency/vault_read.go:96 +0x8b
 github.com/hashicorp/consul-template/dependency.(*VaultReadQuery).Fetch(0xc004c67090, 0xc003704750, 0xc004c67220, 0x1, 0x1, 0x8456f2, 0xc0070c8701, 0xc000c44fa8)
         github.com/hashicorp/consul-template@v0.25.1/dependency/vault_read.go:79 +0xd8
 github.com/hashicorp/consul-template/watch.(*View).fetch(0xc0050c6f00, 0xc002db71a0, 0xc002db72c0, 0xc0033884e0)
         github.com/hashicorp/consul-template@v0.25.1/watch/view.go:204 +0x168
 created by github.com/hashicorp/consul-template/watch.(*View).poll
         github.com/hashicorp/consul-template@v0.25.1/watch/view.go:117 +0x44d

Reproduction steps

See hashicorp/consul-template#1450

This is an issue that gets fixed in consul-template 0.25.2, please update the dependency in nomad side.

[github-actions]

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.