Nomad v0.7.1 will not discover default route on interfaces with a space in the name

Known Issue: Nomad v0.7.1 will not discover default route on interfaces with a space in the name

Affected Versions

• Nomad v0.7.1

Affected Platforms

• All Windows versions

Summary

On Windows, if the interface name for your default route contains a space, Nomad v0.7.1 will fail to start with the following error:

==> Error starting agent: client setup failed: fingerprinting failed: 
Error while detecting network interface during fingerprinting: no
network_interface given and failed to determine interface attached 
to default route

Resolutions

There are a few options to bring your cluster into a starting state:

• Upgrade to a newer Nomad version.
• Use the --network-interface flag on the command line.
  For example, if your default route is on “Ethernet 1”, add --interface-name="Ethernet 1" to your command.

• Set the network_interface explicitly in the client stanza of your Nomad configuration. For example, if your default route is on “Ethernet 1”, your configuration might look like:

  ...
  client {
  ...
      network_interface = "Ethernet 1"
  ...
  }
  ...

• Rename the interface to a name with no spaces.