Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vultr server gather facts fails when firewall is enabled on a VM #48342

Merged
merged 1 commit into from
Nov 9, 2018

Conversation

cleming
Copy link
Contributor

@cleming cleming commented Nov 8, 2018

SUMMARY

vultr_server_facts fails when a VM has a firewall enabled. Works normally without firewall.

ISSUE TYPE
  • Bugfix Pull Request
COMPONENT NAME

vultr_server_facts

ANSIBLE VERSION
ansible 2.7.0
ADDITIONAL INFORMATION

vultr_server_facts with firewall on VM before change:

The full traceback is:
Traceback (most recent call last):
  File "<stdin>", line 113, in <module>
  File "<stdin>", line 105, in _ansiballz_main
  File "<stdin>", line 48, in invoke_module
  File "/tmp/ansible_vultr_server_facts_payload_EYlPlh/__main__.py", line 188, in <module>
  File "/tmp/ansible_vultr_server_facts_payload_EYlPlh/__main__.py", line 180, in main
  File "/tmp/ansible_vultr_server_facts_payload_EYlPlh/ansible_vultr_server_facts_payload.zip/ansible/module_utils/vultr.py", line 268, in get_result
  File "/tmp/ansible_vultr_server_facts_payload_EYlPlh/ansible_vultr_server_facts_payload.zip/ansible/module_utils/vultr.py", line 250, in normalize_result
ValueError: invalid literal for int() with base 10: '8950f8b6'

fatal: [localhost -> localhost]: FAILED! => {
    "changed": false, 
    "module_stderr": "Traceback (most recent call last):\n  File \"<stdin>\", line 113, in <module>\n  File \"<stdin>\", line 105, in _ansiballz_main\n  File \"<stdin>\", line 48, in invoke_module\n  File \"/tmp/ansible_vultr_server_facts_payload_EYlPlh/__main__.py\", line 188, in <module>\n  File \"/tmp/ansible_vultr_server_facts_payload_EYlPlh/__main__.py\", line 180, in main\n  File \"/tmp/ansible_vultr_server_facts_payload_EYlPlh/ansible_vultr_server_facts_payload.zip/ansible/module_utils/vultr.py\", line 268, in get_result\n  File \"/tmp/ansible_vultr_server_facts_payload_EYlPlh/ansible_vultr_server_facts_payload.zip/ansible/module_utils/vultr.py\", line 250, in normalize_result\nValueError: invalid literal for int() with base 10: '8950f8b6'\n", 
    "module_stdout": "", 
    "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", 
    "rc": 1
}

after change: works great.

@ansibot
Copy link
Contributor

ansibot commented Nov 8, 2018

Hi @cleming, thank you for submitting this pull-request!

click here for bot help

@ansibot
Copy link
Contributor

ansibot commented Nov 8, 2018

@ansibot ansibot added affects_2.8 This issue/PR affects Ansible v2.8 bug This issue/PR relates to a bug. cloud community_review In order to be merged, this PR must follow the community review workflow. module This issue/PR relates to a module. needs_triage Needs a first human triage before being processed. new_contributor This PR is the first contribution by a new community member. small_patch support:community This issue/PR relates to code supported by the Ansible community. traceback This issue/PR includes a traceback. labels Nov 8, 2018
Copy link
Contributor

@resmo resmo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

shipit

@resmo
Copy link
Contributor

resmo commented Nov 8, 2018

good catch, thanks.

@ansibot ansibot removed the needs_triage Needs a first human triage before being processed. label Nov 8, 2018
@resmo
Copy link
Contributor

resmo commented Nov 8, 2018

bot_status

@ansibot
Copy link
Contributor

ansibot commented Nov 8, 2018

Components

lib/ansible/modules/cloud/vultr/vultr_server_facts.py
support: community
maintainers: Spredzy resmo

Metadata

waiting_on: maintainer
changes_requested_by: null
needs_info: False
needs_revision: False
needs_rebase: False
merge_commits: []
too many files or commits: False
mergeable_state: clean
shippable_status: success
maintainer_shipits (module maintainers): 0
community_shipits (namespace maintainers): 0
ansible_shipits (core team members): 1
shipit_actors (maintainers or core team members): resmo
shipit_actors_other: []
automerge: automerge shipit test failed

click here for bot help

@resmo resmo merged commit 2436aa1 into ansible:devel Nov 9, 2018
@resmo
Copy link
Contributor

resmo commented Nov 9, 2018

Thanks!

@resmo
Copy link
Contributor

resmo commented Nov 12, 2018

backport PR for 2.7.x #48563

Ghilli3 pushed a commit to Ghilli3/ansible that referenced this pull request Nov 12, 2018
abadger pushed a commit that referenced this pull request Nov 13, 2018
abadger pushed a commit that referenced this pull request Nov 13, 2018
mjmayer pushed a commit to mjmayer/ansible that referenced this pull request Nov 30, 2018
Tomorrow9 pushed a commit to Tomorrow9/ansible that referenced this pull request Dec 4, 2018
@dagwieers dagwieers added the vultr Vultr community label Feb 11, 2019
@ansible ansible locked and limited conversation to collaborators Jul 22, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
affects_2.8 This issue/PR affects Ansible v2.8 bug This issue/PR relates to a bug. cloud community_review In order to be merged, this PR must follow the community review workflow. module This issue/PR relates to a module. new_contributor This PR is the first contribution by a new community member. small_patch support:community This issue/PR relates to code supported by the Ansible community. traceback This issue/PR includes a traceback. vultr Vultr community
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants