You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use hashi-ui a lot and of it's awesome features is to up/down-scale taskgroups. This functionality however got broken with the 0.6 release if you don't have an update {} stanza specified in the job.
Reproduce:
job "example" {
datacenters = ["zone1"]
group "cache" {
count = 1
task "redis" {
driver = "docker"
config {
image = "redis:3.2"
port_map {
db = 6379
}
}
resources {
cpu = 500
memory = 256
network {
mbits = 1
port "db" {}
}
}
service {
name = "global-redis-check"
tags = ["global", "cache"]
port = "db"
check {
name = "alive"
type = "tcp"
interval = "10s"
timeout = "2s"
}
}
}
}
}
Because hashiui fetches this from the API and re-posts the JSON job with an updated count I get the following validation errors from the API:
2017/08/30 11:24:34.306754 [ERR] http: Request /v1/jobs?region=ams1&wait=60000ms, error: 1 error(s) occurred:
* Task group cache validation failed: 1 error(s) occurred:
* 5 error(s) occurred:
* Invalid health check given: ""
* Max parallel can not be less than one: 0 < 1
* Healthy deadline must be greater than zero: 0s
* Minimum healthy time must be less than healthy deadline: 0s > 0s
* Stagger must be greater than zero: 0s
This PR fixes an issue in which we would merge an update stanza from the
job into the task groups even if it was empty. This broke round
tripping a job (reading from the api and resubmitting as JSON)
Fixes#3132
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.
I use hashi-ui a lot and of it's awesome features is to up/down-scale taskgroups. This functionality however got broken with the 0.6 release if you don't have an
update {}
stanza specified in the job.Reproduce:
now
nomad inspect example
shows:Because hashiui fetches this from the API and re-posts the JSON job with an updated count I get the following validation errors from the API:
Issue also posted here jippi/hashi-ui#302
The text was updated successfully, but these errors were encountered: