# Vagrant up failing at: nginx_test failure

**URL:** https://discourse.roots.io/t/vagrant-up-failing-at-nginx-test-failure/7145
**Category:** trellis
**Created:** 2016-07-07T14:47:35Z
**Posts:** 11
**Showing post:** 8 of 11

## Post 8 by @fullyint — 2016-08-05T18:48:23Z

Thanks for your work on this @rpk

Once I update to Ansible 2.1.1.0, I can reproduce the problem on vagrant 1.8.5 (running on OS X).  
If I roll Ansible back to 2.0.2.0 the problem stops.

In addition, on Ansible 2.1.1.0, the `debug` task msg seems to not print when run as part of the handler, but it does print if I put the `reload nginx` include in a regular playbook task file:

```
- include: "{{ playbook_dir }}/roles/common/tasks/reload_nginx.yml"
```

I think the `success` filter had some modifications in Ansible 2.1, which may be responsible for what we’re seeing here. I’ll look into it a bit.

I also tried to reproduce on a staging/production remote with DigitalOcean. If I use Ansible 2.1.1.0 I get other yml errors, which disappear if I roll back to 2.0.2.0.

Could you try rolling your [Ansible version back to 2.0.2.0](https://discourse.roots.io/t/taskinclude-object-has-no-attribute-has-triggered/6834/14) and see if that solves it for now? I guess that’s the only version the [Trellis README](https://github.com/roots/trellis/tree/6ad6fcbb6e0c0cfdaaf7ecb734c2e867ff0437a7#requirements) reports as supported. I thought only [2.1.0.0](https://github.com/roots/trellis/blob/6ad6fcbb6e0c0cfdaaf7ecb734c2e867ff0437a7/roles/common/defaults/main.yml#L4) was problematic, but I actually didn’t know anything about 2.1.1.0 till testing it now.

---

_[View the full topic](https://discourse.roots.io/t/vagrant-up-failing-at-nginx-test-failure/7145)._