{"action":"created","issue":{"url":"https://api.github.com/repos/ansible/ansible/issues/12170","labels_url":"https://api.github.com/repos/ansible/ansible/issues/12170/labels{/name}","comments_url":"https://api.github.com/repos/ansible/ansible/issues/12170/comments","events_url":"https://api.github.com/repos/ansible/ansible/issues/12170/events","html_url":"https://github.com/ansible/ansible/issues/12170","id":104124395,"number":12170,"title":"support for \"serial\" on an individual task","user":{"login":"djudd","id":409126,"avatar_url":"https://avatars.githubusercontent.com/u/409126?v=3","gravatar_id":"","url":"https://api.github.com/users/djudd","html_url":"https://github.com/djudd","followers_url":"https://api.github.com/users/djudd/followers","following_url":"https://api.github.com/users/djudd/following{/other_user}","gists_url":"https://api.github.com/users/djudd/gists{/gist_id}","starred_url":"https://api.github.com/users/djudd/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/djudd/subscriptions","organizations_url":"https://api.github.com/users/djudd/orgs","repos_url":"https://api.github.com/users/djudd/repos","events_url":"https://api.github.com/users/djudd/events{/privacy}","received_events_url":"https://api.github.com/users/djudd/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/ansible/ansible/labels/feature_idea","name":"feature_idea","color":"006b75"},{"url":"https://api.github.com/repos/ansible/ansible/labels/P4","name":"P4","color":"bfe5bf"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":7,"created_at":"2015-08-31T20:04:22Z","updated_at":"2015-10-15T15:29:08Z","closed_at":null,"body":"(Feature Idea)\r\n\r\nThe natural way to handle configuration or other updates that require a rolling restart would be to perform updates in parallel, then notify a handler, which performs a restart with `serial`. But this is not possible, requiring either manual rolling restart or ugly hacks. See https://groups.google.com/forum/#!topic/ansible-project/rBcWzXjt-Xc"},"comment":{"url":"https://api.github.com/repos/ansible/ansible/issues/comments/148423204","html_url":"https://github.com/ansible/ansible/issues/12170#issuecomment-148423204","issue_url":"https://api.github.com/repos/ansible/ansible/issues/12170","id":148423204,"user":{"login":"ehorne","id":10051288,"avatar_url":"https://avatars.githubusercontent.com/u/10051288?v=3","gravatar_id":"","url":"https://api.github.com/users/ehorne","html_url":"https://github.com/ehorne","followers_url":"https://api.github.com/users/ehorne/followers","following_url":"https://api.github.com/users/ehorne/following{/other_user}","gists_url":"https://api.github.com/users/ehorne/gists{/gist_id}","starred_url":"https://api.github.com/users/ehorne/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ehorne/subscriptions","organizations_url":"https://api.github.com/users/ehorne/orgs","repos_url":"https://api.github.com/users/ehorne/repos","events_url":"https://api.github.com/users/ehorne/events{/privacy}","received_events_url":"https://api.github.com/users/ehorne/received_events","type":"User","site_admin":false},"created_at":"2015-10-15T15:29:08Z","updated_at":"2015-10-15T15:29:08Z","body":"+1; however the serial needs not to fail the entire play for remaining hosts if all hosts in the current serial fail. I often have to do rolling restarts, one server at a time across 50+ servers. It sucks when the play fails on server 3 because server 3 had some strange unexpected condition that caused the restart to fail. Setting max_failpercent to something higher than 100% should force ansible to continue the play for remaining hosts. "}}