Panic when running nomad keyring command - Nomad 0.7.0

[jrasell]

Nomad version

$ nomad version
Nomad v0.7.0

Operating system and Environment details

$ lsb_release -a
Distributor ID:	Debian
Description:	Debian GNU/Linux 8.6 (jessie)
Release:	8.6
Codename:	jessie

Issue

When running nomad keyring a panic is experienced. This issue seems to affect running clusters; as well as when running the command locally with no local cluster running nor any connectivity to a running cluster.

All subcommands seem exhibit the same behaviour.

Reproduction steps

Run the command nomad keyring.

Nomad CLI Output

keys flag redefined: token
panic: keys flag redefined: token

goroutine 1 [running]:
flag.(*FlagSet).Var(0xc4203c2cc0, 0x1fcace0, 0xc4203f17b0, 0x159686b, 0x5, 0x159ba84, 0x9)
	/usr/local/go/src/flag/flag.go:793 +0x5e1
flag.(*FlagSet).StringVar(0xc4203c2cc0, 0xc4203f17b0, 0x159686b, 0x5, 0x0, 0x0, 0x159ba84, 0x9)
	/usr/local/go/src/flag/flag.go:696 +0x8b
github.com/hashicorp/nomad/command.(*KeyringCommand).Run(0xc42044c780, 0xc42000c070, 0x0, 0x0, 0xc4203f0d00)
	/opt/gopath/src/github.com/hashicorp/nomad/command/keyring.go:81 +0x2e4
github.com/hashicorp/nomad/vendor/github.com/mitchellh/cli.(*CLI).Run(0xc4203df7c0, 0xc4203df7c0, 0x4a, 0x16010c0)
	/opt/gopath/src/github.com/hashicorp/nomad/vendor/github.com/mitchellh/cli/cli.go:255 +0x1eb
main.RunCustom(0xc42000c070, 0x1, 0x1, 0xc420428840, 0xc420177f60)
	/opt/gopath/src/github.com/hashicorp/nomad/main.go:61 +0x1806
main.Run(0xc42000c070, 0x1, 0x1, 0x11ef956)
	/opt/gopath/src/github.com/hashicorp/nomad/main.go:24 +0x56
main.main()
	/opt/gopath/src/github.com/hashicorp/nomad/main.go:20 +0x63

[schmichael]

Thanks for the report @jrasell. We'll try to look into this ASAP.

Edit: Or maybe you'll be me to it! Thanks again @jrasell!

[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.