You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The variable ansible_processor_vcpus isn't referenced in that task but it is referenced in defaults/main.yml:
netbox_processes: "{{ ansible_processor_vcpus }}"
We changed it to this and it worked:
netbox_processes: "{{ ansible_processor_vcpus | default(4) }}"
I'm not sure why that var is undefined - from what I've read it's supposed to be set automatically somewhere. So I'm not sure if what we've done is the best solution but I'm happy to submit it in a pull request if people think it's OK.
The text was updated successfully, but these errors were encountered:
That change is fine I think, but I believe default(1) would be more appropriate here—wouldn't make too much sense to set it to 4 for example on a 1 core virtual machine/VPS.
We ran the role (v1.0.2) on a host and got this error message:
ASK [lae.netbox : Configure uWSGI NetBox application] **************************************************************************************************************************************************************************************
fatal: [xxx.sol1.net]: FAILED! => {"changed": false, "msg": "AnsibleUndefinedVariable: {{ ansible_processor_vcpus }}: 'ansible_processor_vcpus' is undefined"}
The variable ansible_processor_vcpus isn't referenced in that task but it is referenced in defaults/main.yml:
netbox_processes: "{{ ansible_processor_vcpus }}"
We changed it to this and it worked:
netbox_processes: "{{ ansible_processor_vcpus | default(4) }}"
I'm not sure why that var is undefined - from what I've read it's supposed to be set automatically somewhere. So I'm not sure if what we've done is the best solution but I'm happy to submit it in a pull request if people think it's OK.
The text was updated successfully, but these errors were encountered: