seems to work ok here

seems to work fine here

seems ok here

seems ok here

seems ok here

seems ok here

seems ok here

seems ok here

works here in casual testing

seems ok to me

seems to work fine here

This update has been unpushed.

Should have been obsoleted by newer update.

Yep. Sadly confirm here too.

Ansible 2.0 is (with a few rare exceptions where it rejects something that 1.9.x permitted, but was incorrect) compatible playbook wise with 1.9.x.

Could everyone here who has hit a playbook that doesn't work with 2.0, but does work with 1.9 file a ticket upstream or a bug report in bugzilla. We want upstream ansible to fix these cases and release 2.0.x with those fixes before we push to stable.

Ansible 2.0 is (with a few rare exceptions where it rejects something that 1.9.x permitted, but was incorrect) compatible playbook wise with 1.9.x.

Could everyone here who has hit a playbook that doesn't work with 2.0, but does work with 1.9 file a ticket upstream or a bug report in bugzilla. We want upstream ansible to fix these cases and release 2.0.x with those fixes before we push to stable.

Ansible 2.0 is (with a few rare exceptions where it rejects something that 1.9.x permitted, but was incorrect) compatible playbook wise with 1.9.x.

Could everyone here who has hit a playbook that doesn't work with 2.0, but does work with 1.9 file a ticket upstream or a bug report in bugzilla. We want upstream ansible to fix these cases and release 2.0.x with those fixes before we push to stable.

This update has been unpushed.

Should have been obsoleted by newer update.

This update has been unpushed.