# What has changed in terms of sudo in Ansible 2.1

**URL:** <https://forum.ansible.com/t/what-has-changed-in-terms-of-sudo-in-ansible-2-1/21942>\
**Category:** Ansible Project\
**Created:** [July 7, 2016, 12:24am UTC](https://forum.ansible.com/t/what-has-changed-in-terms-of-sudo-in-ansible-2-1/21942 "2016-07-07T00:24:36Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sebin](https://avatars.discourse-cdn.com/v4/letter/s/50afbb/32.png) [@Sebin](https://forum.ansible.com/u/Sebin)\
**Post date:** [July 7, 2016, 12:24am UTC](https://forum.ansible.com/t/what-has-changed-in-terms-of-sudo-in-ansible-2-1/21942/1 "2016-07-07T00:24:36Z")

</div>

Hi All,

I have recently switched to Ansible 2.1 from Ansible 2.0

Surprisingly in one of my environments the playbooks and ad-hoc commands do not run when executed with **sudo**.

is there any way I can debug this to find out what is causing the issues?

Since the only change is the ansible version, I suspect it is something changed in Ansible.

I can still work execute playbooks with the older installation of Ansible 2.0

Thanks

Sebin