-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
check_restart within service block is not recognized #3713
Comments
Hi, thanks for letting us know about this issue. Do you mind including the job configuration where you see this error? |
This is currently broken and should be removed from docs until a fix is released. See #3713
@chelseakomlo hi! sure, here is an example job file that reproduces the issue: job "test" {
type = "service"
region = "global"
datacenters = ["dc1"]
update {
max_parallel = 1
canary = 5
min_healthy_time = "30s"
healthy_deadline = "10m"
auto_revert = true
}
group "mygroup" {
count = 2
task "mytask" {
driver = "exec"
config {
command = "/bin/sleep"
args = ["1"]
}
resources {
network {
mbits = 1
port "mytask" {}
}
}
service {
port = "mytask"
check {
type = "tcp"
port = "mytask"
interval = "10s"
timeout = "2s"
}
check_restart {
limit = 3
grace = "90s"
ignore_warnings = false
}
}
}
}
} |
This is currently broken and should be removed from docs until a fix is released. See #3713
Fixed but forgot to close. Sorry! |
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. |
Nomad version
$ nomad version
Nomad v0.7.1
Issue
check_restart not recognized at service block level as documented in https://www.nomadproject.io/docs/job-specification/check_restart.html
Reproduction steps
Define a
check_restart
block within aservice
block. You will get the following message:The text was updated successfully, but these errors were encountered: