{"action":"opened","issue":{"url":"https://api.github.com/repos/hashicorp/nomad/issues/2067","repository_url":"https://api.github.com/repos/hashicorp/nomad","labels_url":"https://api.github.com/repos/hashicorp/nomad/issues/2067/labels{/name}","comments_url":"https://api.github.com/repos/hashicorp/nomad/issues/2067/comments","events_url":"https://api.github.com/repos/hashicorp/nomad/issues/2067/events","html_url":"https://github.com/hashicorp/nomad/issues/2067","id":194288286,"number":2067,"title":"Fail to update when static ports are busy","user":{"login":"samber","id":2951285,"avatar_url":"https://avatars.githubusercontent.com/u/2951285?v=3","gravatar_id":"","url":"https://api.github.com/users/samber","html_url":"https://github.com/samber","followers_url":"https://api.github.com/users/samber/followers","following_url":"https://api.github.com/users/samber/following{/other_user}","gists_url":"https://api.github.com/users/samber/gists{/gist_id}","starred_url":"https://api.github.com/users/samber/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/samber/subscriptions","organizations_url":"https://api.github.com/users/samber/orgs","repos_url":"https://api.github.com/users/samber/repos","events_url":"https://api.github.com/users/samber/events{/privacy}","received_events_url":"https://api.github.com/users/samber/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-12-08T09:40:54Z","updated_at":"2016-12-08T09:40:54Z","closed_at":null,"body":"Hi guys,\r\n\r\nI just found an abnormal behaviour:\r\n\r\nI am running 3 Nomad nodes in client mode, each running a RabbitMQ container with static ports. For my test (and probably for production as well), my ```max_parallel``` (stanza ```update```) is equal to ```count``` (stanza ```group```). \r\n\r\nWhen I update the job file, then apply it, Nomad try to start 3 new containers before stopping old RabbitMQ instances. Unfortunately, because I have only 3 nodes, ports are already busy: new containers cannot start, but old instances are killed anyway.\r\n\r\nCould you implement a retry or manage this special case ? It would be pity to have to start 3 more vm, only for rolling-upgrade !"}}
{"actor":{"display_login":"samber"}}