# Scale node  error "AnsibleUndefinedVariable: 'dict object' has no attribute 'address'"

**URL:** <https://forum.ansible.com/t/scale-node-error-ansibleundefinedvariable-dict-object-has-no-attribute-address/30450>\
**Category:** Ansible Project\
**Tags:** kubernetes\
**Created:** [May 30, 2019, 3:30pm UTC](https://forum.ansible.com/t/scale-node-error-ansibleundefinedvariable-dict-object-has-no-attribute-address/30450 "2019-05-30T15:30:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Van\_Nguyen\_Hoang](https://avatars.discourse-cdn.com/v4/letter/v/a587f6/32.png) [@Van\_Nguyen\_Hoang](https://forum.ansible.com/u/Van_Nguyen_Hoang)\
**Post date:** [May 30, 2019, 3:30pm UTC](https://forum.ansible.com/t/scale-node-error-ansibleundefinedvariable-dict-object-has-no-attribute-address/30450/1 "2019-05-30T15:30:15Z")

</div>

Dear All,

I’m newbie kubernetes and kubespray. When i add new node to cluster, i had error message:

TASK [etcd : Gen\_certs | write openssl config] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
Thursday 30 May 2019 22:29:47 +0700 (0:00:00.265) 0:01:21.954 \*\*\*\*\*\*\*\*\*\*  
fatal: [node1 → 172.16.20.133]: FAILED! =\> {“changed”: false, “msg”: “AnsibleUndefinedVariable: ‘dict object’ has no attribute ‘address’”}

Please help me fix it. Tks!

---

<div class="post-metadata">

**Author:** ![erik\_clark](https://avatars.discourse-cdn.com/v4/letter/e/ba8739/32.png) [@erik\_clark](https://forum.ansible.com/u/erik_clark)\
**Post date:** [May 30, 2019, 4:26pm UTC](https://forum.ansible.com/t/scale-node-error-ansibleundefinedvariable-dict-object-has-no-attribute-address/30450/2 "2019-05-30T16:26:46Z")

</div>

You need to paste the task and sample output from the task being processed in later tasks. Without it, we can’t really identify what is stored in the variable to start with.

Have you done a

- debug:  
var=(your var here)

to see what the data structure looks like to ansible?