-
Notifications
You must be signed in to change notification settings - Fork 24.1k
Undefined variables in boundary_meter #29387
Copy link
Copy link
Closed
Labels
affects_2.2This issue/PR affects Ansible v2.2This issue/PR affects Ansible v2.2bugThis issue/PR relates to a bug.This issue/PR relates to a bug.moduleThis issue/PR relates to a module.This issue/PR relates to a module.support:communityThis issue/PR relates to code supported by the Ansible community.This issue/PR relates to code supported by the Ansible community.
Description
Metadata
Metadata
Assignees
Labels
affects_2.2This issue/PR affects Ansible v2.2This issue/PR affects Ansible v2.2bugThis issue/PR relates to a bug.This issue/PR relates to a bug.moduleThis issue/PR relates to a module.This issue/PR relates to a module.support:communityThis issue/PR relates to code supported by the Ansible community.This issue/PR relates to code supported by the Ansible community.
Type
Fields
Give feedbackNo fields configured for issues without a type.
From @abadger on 2016-10-23T23:16:22Z
ISSUE TYPE
COMPONENT NAME
monitoring/boundary_meter.py
ANSIBLE VERSION
SUMMARY
When porting to python3 I ran pyflakes on boundary_meter.py and found that there are several undefined variables. These probably make state=absent traceback and state=present when the cert file needs to be downloaded.
delete_meter problem
https://github.com/ansible/ansible-modules-extras/blob/devel/monitoring/boundary_meter.py#L191
action is used here but not defined at this point in the code.
create_meter problems
https://github.com/ansible/ansible-modules-extras/blob/devel/monitoring/boundary_meter.py#L216
At this point result is not defined. Perhaps you meant response instead?
Copied from original issue: ansible/ansible-modules-extras#3277