# Issue with role variables

**URL:** <https://forum.ansible.com/t/issue-with-role-variables/20223>\
**Category:** Ansible Project\
**Tags:** ubuntu\
**Created:** [January 15, 2016, 3:23am UTC](https://forum.ansible.com/t/issue-with-role-variables/20223 "2016-01-15T03:23:52Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ryan\_Hunter](https://avatars.discourse-cdn.com/v4/letter/r/77aa72/32.png) [@Ryan\_Hunter](https://forum.ansible.com/u/Ryan_Hunter)\
**Post date:** [January 15, 2016, 3:23am UTC](https://forum.ansible.com/t/issue-with-role-variables/20223/1 "2016-01-15T03:23:52Z")

</div>

Hello

I just upgraded to ansible 2.0.0.0 and am having some backwards compatibility issues:

If I have a play like:

- hosts: uber  
user: ubuntu  
roles:
- role: zuul  
name: uber  
port: “{{ uber\_zuul\_port }}”  
workers:
- localhost  
worker\_port: “{{ uber\_port }}”
- uber

I keep getting:

fatal: [default]: FAILED! =\> {“failed”: true, “msg”: “ERROR! ‘port’ is undefined”}

in the role zuul.

This play works fine with ansible 1.9 Did something related to role parameterization get deprecated?

Thanks