# 'Odd' Behavior with Role Dependencies when using import\_role **URL:** \ **Category:** Ansible Project\ **Created:** [March 17, 2021, 8:30pm UTC](https://forum.ansible.com/t/odd-behavior-with-role-dependencies-when-using-import-role/34803 "2021-03-17T20:30:56Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Todd\_Beauchemin](https://avatars.discourse-cdn.com/v4/letter/t/b9e5f3/32.png) [@Todd\_Beauchemin](https://forum.ansible.com/u/Todd_Beauchemin)\ **Post date:** [March 17, 2021, 8:30pm UTC](https://forum.ansible.com/t/odd-behavior-with-role-dependencies-when-using-import-role/34803/1 "2021-03-17T20:30:56Z")
We’ve seen what we’d classify as odd behavior when using import\_role with roles that have dependencies defined under the meta directory. The version of Ansible we are running is 2.9.10. We have a few roles setup as follows - base\_role - Does some basic setup of directories for storing facts and has some tasks focused around providing debug messages such as displaying known variables and facts as well as installing some utility packages - Has no dependencies and has ‘allow\_duplicates’ explicitly set to ‘false’ - network\_role - Handles configuration of network related items such as firewall, interface options, DNS resolver, etc. - Depends on base\_role under meta/main.yaml and also has ‘allow\_duplicates’ explicitly set to ‘false’ - cron\_role ---
**Author:** ![sivel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sivel/32/1198_2.png) [@sivel](https://forum.ansible.com/u/sivel)\ **Post date:** [March 17, 2021, 8:53pm UTC](https://forum.ansible.com/t/odd-behavior-with-role-dependencies-when-using-import-role/34803/2 "2021-03-17T20:53:51Z")
You didn’t make it easy to reproduce, but I think I created a reproducer. Based on my reproducer, your issue has been fixed in [https://github.com/ansible/ansible/pull/72208](https://github.com/ansible/ansible/pull/72208)