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

Fix connection error reporting #40758

Conversation

caphrim007
Copy link
Contributor

SUMMARY

The variables used for reporting errors were incorrect. Additionally,
the fetching of connection related params was using an old format.

ISSUE TYPE
  • Bugfix Pull Request
COMPONENT NAME

f5 module utils

ANSIBLE VERSION
ansible 2.6.0
  config file = /here/test/integration/ansible.cfg
  configured module search path = ['/here/library/modules']
  ansible python module location = /usr/local/lib/python3.6/site-packages/ansible
  executable location = /usr/local/bin/ansible
  python version = 3.6.5 (default, May  5 2018, 03:09:35) [GCC 4.9.2]
ADDITIONAL INFORMATION

The variables used for reporting errors were incorrect. Additionally,
the fetching of connection related params was using an old format.
@ansibot
Copy link
Contributor

ansibot commented May 27, 2018

@ansibot ansibot added affects_2.6 This issue/PR affects Ansible v2.6 bug This issue/PR relates to a bug. needs_triage Needs a first human triage before being processed. networking Network category python3 support:core This issue/PR relates to code supported by the Ansible Engineering Team. labels May 27, 2018
@caphrim007 caphrim007 removed the needs_triage Needs a first human triage before being processed. label May 27, 2018
@caphrim007 caphrim007 merged commit dc08bca into ansible:devel May 27, 2018
caphrim007 added a commit to caphrim007/ansible that referenced this pull request May 27, 2018
The variables used for reporting errors were incorrect. Additionally,
the fetching of connection related params was using an old format.

(cherry picked from commit dc08bca)
caphrim007 added a commit that referenced this pull request May 27, 2018
The variables used for reporting errors were incorrect. Additionally,
the fetching of connection related params was using an old format.

(cherry picked from commit dc08bca)
gothicx pushed a commit to gothicx/ansible that referenced this pull request Jun 9, 2018
The variables used for reporting errors were incorrect. Additionally,
the fetching of connection related params was using an old format.
jacum pushed a commit to jacum/ansible that referenced this pull request Jun 26, 2018
The variables used for reporting errors were incorrect. Additionally,
the fetching of connection related params was using an old format.
@caphrim007 caphrim007 deleted the bugfix.fix-incorrect-connection-error-output branch August 28, 2018 17:13
@ansible ansible locked and limited conversation to collaborators May 29, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
affects_2.6 This issue/PR affects Ansible v2.6 bug This issue/PR relates to a bug. networking Network category python3 support:core This issue/PR relates to code supported by the Ansible Engineering Team.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants