Undefined variables in boundary_meter

[ansibot]

From @abadger on 2016-10-23T23:16:22Z

ISSUE TYPE

• Bug Report

COMPONENT NAME

monitoring/boundary_meter.py

ANSIBLE VERSION

devel 2.2

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

[ansibot]

From @ansibot on 2016-10-23T23:16:22Z

@ccollicutt ping, this issue is waiting for your response.
click here for bot help

[ansibot]

From @ccollicutt on 2016-10-23T23:16:22Z

Hi, I don't think boundary exists as a service any more, so I'm sorry but this module should just be removed. I actually thought it had been. My apologies.

[jborean93]

The service no longer exists so this module will no longer work, the module was removed in #31506 and won't be available in future Ansible versions.