# Ansible 2.0 ec2\_lc classic\_link\_vpc\_id error

**URL:** <https://forum.ansible.com/t/ansible-2-0-ec2-lc-classic-link-vpc-id-error/20213>\
**Category:** Ansible Project\
**Tags:** ubuntu\
**Created:** [January 14, 2016, 2:08pm UTC](https://forum.ansible.com/t/ansible-2-0-ec2-lc-classic-link-vpc-id-error/20213 "2016-01-14T14:08:15Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jari\_Kujansuu](https://avatars.discourse-cdn.com/v4/letter/j/7ea924/32.png) [@Jari\_Kujansuu](https://forum.ansible.com/u/Jari_Kujansuu)\
**Post date:** [January 14, 2016, 2:08pm UTC](https://forum.ansible.com/t/ansible-2-0-ec2-lc-classic-link-vpc-id-error/20213/1 "2016-01-14T14:08:15Z")

</div>

Hi,

I am trying to figure out what could be problem when I upgraded Ansible to 2.0 (actually 2.0.0.1) and added into ec2\_lc configuration lines for classic\_link\_vpc\_id and classic\_link\_vpc\_security\_groups but get following error:

TypeError: **init** () got an unexpected keyword argument ‘classic\_link\_vpc\_id’

Machine has Python 2.7.9 and when someone had same error it was fixed by upgrading from 2.6.6 to 2.7.10 (in 2.0.0 RC1 - [https://github.com/ansible/ansible-modules-core/issues/2601](https://github.com/ansible/ansible-modules-core/issues/2601)) and was wondering could that be possible reason and should I try that? Its Ubuntu and latest Python that is available for it is 2.7.9 and if not necessary wouldn’t want to try to build it from sources or something.