News HashiCorp to join IBM to accelerate multi-cloud automation. Read the blog →
Nomad
Nomad Home

Command: deployment fail

The deployment fail command is used to mark a deployment as failed. Failing a deployment will stop the placement of new allocations as part of rolling deployment and if the job is configured to auto revert, the job will attempt to roll back to a stable version.

Usage

nomad deployment fail [options] <deployment id>

The deployment fail command requires a single argument, a deployment ID or prefix.

When ACLs are enabled, this command requires a token with the submit-job and read-job capabilities for the deployment's namespace.

General Options

  • -address=<addr>: The address of the Nomad server. Overrides the NOMAD_ADDR environment variable if set. Defaults to http://127.0.0.1:4646.

  • -region=<region>: The region of the Nomad server to forward commands to. Overrides the NOMAD_REGION environment variable if set. Defaults to the Agent's local region.

  • -namespace=<namespace>: The target namespace for queries and actions bound to a namespace. Overrides the NOMAD_NAMESPACE environment variable if set. If set to '*', subcommands which support this functionality query all namespaces authorized to user. Defaults to the "default" namespace.

  • -no-color: Disables colored command output. Alternatively, NOMAD_CLI_NO_COLOR may be set. This option takes precedence over -force-color.

  • -force-color: Forces colored command output. This can be used in cases where the usual terminal detection fails. Alternatively, NOMAD_CLI_FORCE_COLOR may be set. This option has no effect if -no-color is also used.

  • -ca-cert=<path>: Path to a PEM encoded CA cert file to use to verify the Nomad server SSL certificate. Overrides the NOMAD_CACERT environment variable if set.

  • -ca-path=<path>: Path to a directory of PEM encoded CA cert files to verify the Nomad server SSL certificate. If both -ca-cert and -ca-path are specified, -ca-cert is used. Overrides the NOMAD_CAPATH environment variable if set.

  • -client-cert=<path>: Path to a PEM encoded client certificate for TLS authentication to the Nomad server. Must also specify -client-key. Overrides the NOMAD_CLIENT_CERT environment variable if set.

  • -client-key=<path>: Path to an unencrypted PEM encoded private key matching the client certificate from -client-cert. Overrides the NOMAD_CLIENT_KEY environment variable if set.

  • -tls-server-name=<value>: The server name to use as the SNI host when connecting via TLS. Overrides the NOMAD_TLS_SERVER_NAME environment variable if set.

  • -tls-skip-verify: Do not verify TLS certificate. This is highly not recommended. Verification will also be skipped if NOMAD_SKIP_VERIFY is set.

  • -token: The SecretID of an ACL token to use to authenticate API requests with. Overrides the NOMAD_TOKEN environment variable if set.

Fail Options

  • -detach: Return immediately instead of monitoring. A new evaluation ID will be output, which can be used to examine the evaluation using the eval status command.

  • -verbose: Show full information.

Examples

Manually mark an ongoing deployment as failed:

$ nomad deployment fail 8990cfbcDeployment "8990cfbc-28c0-cb28-ca31-856cf691b987" failed ==> Monitoring evaluation "a2d97ad5"    Evaluation triggered by job "example"    Evaluation within deployment: "8990cfbc"    Evaluation status changed: "pending" -> "complete"==> Evaluation "a2d97ad5" finished with status "complete" $ nomad deployment status 8990cfbcID          = 8990cfbcJob ID      = exampleJob Version = 2Status      = failedDescription = Deployment marked as failed DeployedTask Group  Desired  Placed  Healthy  Unhealthycache       3        2       1        0
Edit this page on GitHub