status
stringclasses 1
value | repo_name
stringlengths 9
24
| repo_url
stringlengths 28
43
| issue_id
int64 1
104k
| updated_files
stringlengths 8
1.76k
| title
stringlengths 4
369
| body
stringlengths 0
254k
⌀ | issue_url
stringlengths 37
56
| pull_url
stringlengths 37
54
| before_fix_sha
stringlengths 40
40
| after_fix_sha
stringlengths 40
40
| report_datetime
timestamp[ns, tz=UTC] | language
stringclasses 5
values | commit_datetime
timestamp[us, tz=UTC] |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
closed | ansible/ansible | https://github.com/ansible/ansible | 62,231 | ["docs/docsite/rst/dev_guide/developing_collections.rst", "docs/docsite/rst/dev_guide/developing_inventory.rst", "docs/docsite/rst/dev_guide/developing_plugins.rst", "docs/docsite/rst/plugins/cache.rst", "docs/docsite/rst/plugins/callback.rst", "docs/docsite/rst/plugins/inventory.rst"] | Unclear how to use inventory plugins in collections | <!--- Verify first that your issue is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
<!--- Explain the problem briefly below -->
I've been unable to get inventory plugins working inside of collections. The inventory plugin in ansible/ansible always takes precedence.
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
<!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure -->
collections
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
devel
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
I've got a inventory.gcp.yml file that I run with `ansible-inventory --list -i inventory.gcp.yml`. I've got a collection called google.cloud installed into my collections path. Here are the various things I've tried.
```yaml
plugin: gcp_compute
...
```
Result: Runs the ansible/ansible inventory plugin.
```yaml
collections:
- google.cloud
plugin: gcp_compute
...
```
Result: Runs the ansible/ansible inventory plugin
```yaml
plugin: google.cloud.gcp_compute
...
```
Result: Plugin not found, errors out.
(I've also tried with `google.cloud.plugins.inventory.gcp_compute` and `google.cloud.inventory.gcp_compute` to no avail)
<!--- Paste example playbooks or commands between quotes below -->
```yaml
```
<!--- HINT: You can paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
##### ACTUAL RESULTS
<!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) -->
<!--- Paste verbatim command output between quotes -->
```paste below
```
| https://github.com/ansible/ansible/issues/62231 | https://github.com/ansible/ansible/pull/62465 | de515522b69e09f3c274068f48e69187702139c8 | d41050b28b2d3e8d4a97ce13344b04fc87f703a2 | 2019-09-12T22:44:12Z | python | 2019-09-26T16:00:26Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 62,227 | ["changelogs/fragments/63432-openssl_csr-version.yml", "docs/docsite/rst/porting_guides/porting_guide_2.10.rst", "lib/ansible/modules/crypto/openssl_csr.py"] | Setting openssl_csr version has no effect | ##### SUMMARY
Setting [openssl_csr](https://docs.ansible.com/ansible/latest/modules/openssl_csr_module.html)'s `version` parameter has no effect in ansible 2.8.4; it always remains the default (1).
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
openssl_csr
##### ANSIBLE VERSION
```
ansible 2.8.4
config file = /etc/ansible/ansible.cfg
configured module search path = [u'/home/bilge/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python2.7/dist-packages/ansible
executable location = /usr/bin/ansible
python version = 2.7.15+ (default, Nov 27 2018, 23:36:35) [GCC 7.3.0]
```
##### CONFIGURATION
```yaml
- name: Generate CSR
openssl_csr:
privatekey_path: /tmp/private.pem
path: /tmp/csr
subject_alt_name: DNS:example.com
version: 3
```
##### EXPECTED RESULTS
```
Certificate Request:
Data:
Version: 3 (0x2)
```
##### ACTUAL RESULTS
>$ openssl req -in /tmp/csr -noout -text
```
Certificate Request:
Data:
Version: 1 (0x0)
``` | https://github.com/ansible/ansible/issues/62227 | https://github.com/ansible/ansible/pull/63432 | d00d0c81b379f4232421ec01a104b3ce1c6e2820 | ba686154b98194de04a0c37970a3b997394ab7be | 2019-09-12T20:44:37Z | python | 2019-10-17T08:42:05Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 62,224 | ["docs/docsite/rst/community/committer_guidelines.rst", "docs/docsite/rst/community/development_process.rst", "docs/docsite/rst/community/documentation_contributions.rst", "docs/docsite/rst/community/index.rst", "docs/docsite/rst/community/maintainers.rst", "docs/docsite/rst/community/other_tools_and_programs.rst", "docs/docsite/rst/community/reporting_bugs_and_features.rst", "docs/docsite/rst/dev_guide/style_guide/index.rst"] | Remove Latin phrases from the docs | ##### SUMMARY
Latin words and phrases like `e.g.` or `etc.` are easily understood by native English speakers and speakers of European languages who speak some English. They are harder to understand for speakers of Asian languages who speak some English. They are also tricky for automated translation.
Add a row to the Style Guide cheat-sheet about avoiding Latin words and phrases.
Remove existing Latin words and phrases from the documentation.
##### ISSUE TYPE
- Documentation Report
##### COMPONENT NAME
docs.ansible.com
##### ANSIBLE VERSION
all
##### CONFIGURATION
N/A
##### OS / ENVIRONMENT
N/A
| https://github.com/ansible/ansible/issues/62224 | https://github.com/ansible/ansible/pull/62419 | 8b9c2533b5d6a64de1f79015ac590c119d51a5d1 | e7436e278f8945dd73b066c47280c1a17bc18ebe | 2019-09-12T20:03:46Z | python | 2019-09-26T19:12:24Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 62,136 | ["changelogs/fragments/62136_strip_spaces_from_action_names.yml", "lib/ansible/parsing/mod_args.py", "test/integration/targets/parsing/roles/test_good_parsing/tasks/main.yml"] | whitespace breaks module name parsing in local_action | <!--- Verify first that your issue is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
Extra whitespace between a local_action module and the first argument is treated as part of the module name and leads to 'module not found' errors in 2.8.4. (It works in 2.7.0.)
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
<!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure -->
ansible-playbook
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
ansible 2.8.4
config file = None
configured module search path = [u'/home/centos/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python2.7/site-packages/ansible
executable location = /usr/bin/ansible
python version = 2.7.5 (default, Jun 20 2019, 20:27:34) [GCC 4.8.5 20150623 (Red Hat 4.8.5-36)]
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
<nothing>
```
##### OS / ENVIRONMENT
CentOS Linux release 7.6.1810 (Core)
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
<!--- Paste example playbooks or commands between quotes below -->
```yaml
- hosts: localhost
gather_facts: false
tasks:
- name: one space
local_action: set_fact a="a"
- name: more spaces
local_action: set_fact b="b"
```
##### EXPECTED RESULTS
all ok; as with 2.7.0:
```
...
PLAY RECAP *****************************************************************************************************************************************************
localhost : ok=3 changed=1 unreachable=0 failed=0
```
##### ACTUAL RESULTS
fails; note the whitespace after 'set_facts' in the error message
```
PLAY [localhost] ***********************************************************************************************************************************************
TASK [one space] ***********************************************************************************************************************************************
ok: [localhost -> localhost]
TASK [more spaces] *********************************************************************************************************************************************
fatal: [localhost]: FAILED! => {"msg": "The module set_fact was not found in configured module paths. Additionally, core modules are missing. If this is a checkout, run 'git pull --rebase' to correct this problem."}
PLAY RECAP *****************************************************************************************************************************************************
localhost : ok=1 changed=0 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0
```
| https://github.com/ansible/ansible/issues/62136 | https://github.com/ansible/ansible/pull/71040 | 701c638757949280c875edc0eb364ee0e63db4bb | 74c14c67439ff2d5e24dfb142c7fadf701fb6712 | 2019-09-11T13:29:28Z | python | 2020-08-03T15:30:45Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 62,128 | ["lib/ansible/modules/notification/hall.py"] | hall module: the hall.com is not available | ##### SUMMARY
hall module: the hall.com is not available
```
19 description:
20 - "The C(hall) module connects to the U(https://hall.com) messaging API and allows you to deliver notication messages to rooms."
...
24 room_token:
25 description:
26 - "Room token provided to you by setting up the Ansible room integation on U(https://hall.com)"
...
65 HALL_API_ENDPOINT = 'https://hall.com/api/1/services/generic/%s'
```
It looks like https://hall.com is not available
```
test:~$ ping hall.com
ping: hall.com: No address associated with hostname
test:~$ ping www.hall.com
ping: www.hall.com: Name or service not known
test:~$ host hall.com
hall.com mail is handled by 10 mxa.mailgun.org.
hall.com mail is handled by 20 mxb.mailgun.org.
test:~$ host www.hall.com
Host www.hall.com not found: 3(NXDOMAIN)
```
I can't find any information about this service exists nowadays or not
Therefore, the module must be removed or fixed.
##### ISSUE TYPE
- Documentation Report
##### COMPONENT NAME
```lib/ansible/modules/notification/hall.py```
##### ANSIBLE VERSION
```
2.8
``` | https://github.com/ansible/ansible/issues/62128 | https://github.com/ansible/ansible/pull/62152 | 5b3526535c9e2f9e117e73d8fbea24b6f9c849ef | 8b42de29fac4093c976478ee893845c06ed4bcd6 | 2019-09-11T09:01:53Z | python | 2019-09-11T19:33:03Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 62,113 | ["test/lib/ansible_test/_data/pytest/plugins/ansible_pytest_collections.py", "test/lib/ansible_test/_data/pytest/plugins/ansible_pytest_coverage.py", "test/lib/ansible_test/_internal/units/__init__.py"] | Imports from `ansible_collections` don't work in `conftest` modules. | ##### SUMMARY
(converted from project card created by @webknjaz)
When conftest in unit test contains something like `from ansible_collections.yum_unit_test_migration_spec.yum_collection.tests.unit.compat.mock import patch`, it will result in `E ModuleNotFoundError: No module named 'ansible_collections'`.
The workaround is to add a boilerplate `conftest.py` into tests root: https://github.com/webknjaz/fqcn_conftest_repro/commit/b07826c54e01c6965cb63aa0a8cada602a311911
##### COMPONENT NAME
ansible-test
##### ANSIBLE VERSION
devel
##### CONFIGURATION
N/A
##### OS / ENVIRONMENT
N/A
##### STEPS TO REPRODUCE
Repro: https://github.com/webknjaz/fqcn_conftest_repro/tree/77347551f5fdd5185b26c752074878ea37055b77
Failure demo: https://github.com/webknjaz/fqcn_conftest_repro/runs/216648897#step:5:41
Hack demo: https://github.com/webknjaz/fqcn_conftest_repro/runs/216654164#step:5:65
##### EXPECTED RESULTS
Tests pass.
##### ACTUAL RESULTS
Tests fail.
| https://github.com/ansible/ansible/issues/62113 | https://github.com/ansible/ansible/pull/62119 | 9b149917a63ead90f49918632cb64ea2892f50da | aaa6d2ecb079498eab9f7f3b32f30c89378818d4 | 2019-09-11T02:39:46Z | python | 2019-09-11T06:27:05Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 62,105 | ["changelogs/fragments/ansible-test-virtualenv-venv.yml", "test/lib/ansible_test/_data/virtualenvcheck.py", "test/lib/ansible_test/_internal/venv.py"] | ansible-test is removing the pip and setuptools | <!--- Verify first that your issue is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
<!--- Explain the problem briefly below -->
When I initiate a virtualenv with python 3.7 and then installing
https://pypi.org/project/ansible/2.9.0b1/
inside it. Running sanity tests is causing the pip package to be removed from the venv
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
<!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure -->
/bin/ansible-test
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
Same also happens with the latest stable-2.9 branch too
```paste below
ansible==2.9.0b1
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
<!--- Paste example playbooks or commands between quotes below -->
```yaml
(.venv) abehl@ansh ~/.ansible/collections/ansible_collections/sensu/sensu_go which pip
/tmp/an/.venv/bin/pip
(.venv) abehl@ansh ~/.ansible/collections/ansible_collections/sensu/sensu_go ansible-test sanity --python 3.7 --requirements
...
(.venv) ✘ abehl@ansh ~/.ansible/collections/ansible_collections/sensu/sensu_go which pip
/usr/local/bin/pip
(.venv) abehl@ansh ~/.ansible/collections/ansible_collections/sensu/sensu_go pip freeze
ansible==2.9.0b1
```
<!--- HINT: You can paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
pip should not be removed
##### ACTUAL RESULTS
<!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) -->
<!--- Paste verbatim command output between quotes -->
```paste below
```
| https://github.com/ansible/ansible/issues/62105 | https://github.com/ansible/ansible/pull/62111 | cd8161a94827bd8dbae53610318f5957b56b8b98 | a7bc11ce67ee58f384c82b6dcae4feede19044a5 | 2019-09-10T21:29:20Z | python | 2019-09-11T02:27:12Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 62,096 | ["changelogs/fragments/62096-test-coverage-all.yml", "test/lib/ansible_test/_internal/cover.py"] | --all flag with ansible-test coverage throws a traceback | <!--- Verify first that your issue is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
<!--- Explain the problem briefly below -->
traceback with --all option with ansible-test coverage
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
<!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure -->
/bin/ansible-test
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
stable 2.9
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
Run coverage with below comand
<!--- Paste example playbooks or commands between quotes below -->
```yaml
ansible-test coverage html --all
```
<!--- HINT: You can paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
No traceback should occure
##### ACTUAL RESULTS
<!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) -->
<!--- Paste verbatim command output between quotes -->
```paste below
Traceback (most recent call last):
File "/home/abehl/work/src/anshul_ansible/ansible/bin/ansible-test", line 28, in <module>
main()
File "/home/abehl/work/src/anshul_ansible/ansible/bin/ansible-test", line 24, in main
cli_main()
File "/home/abehl/work/src/anshul_ansible/ansible/test/lib/ansible_test/_internal/cli.py", line 128, in main
args.func(config)
File "/home/abehl/work/src/anshul_ansible/ansible/test/lib/ansible_test/_internal/cover.py", line 343, in command_coverage_html
output_files = command_coverage_combine(args)
File "/home/abehl/work/src/anshul_ansible/ansible/test/lib/ansible_test/_internal/cover.py", line 73, in command_coverage_combine
paths = _command_coverage_combine_powershell(args) + _command_coverage_combine_python(args)
File "/home/abehl/work/src/anshul_ansible/ansible/test/lib/ansible_test/_internal/cover.py", line 182, in _command_coverage_combine_python
updated.write_file(output_file)
File "/home/abehl/work/src/anshul_ansible/ansible/venv3/lib/python3.7/site-packages/coverage/data.py", line 468, in write_file
self.write_fileobj(fdata)
File "/home/abehl/work/src/anshul_ansible/ansible/venv3/lib/python3.7/site-packages/coverage/data.py", line 461, in write_fileobj
json.dump(file_data, file_obj, separators=(',', ':'))
File "/usr/lib64/python3.7/json/__init__.py", line 179, in dump
for chunk in iterable:
File "/usr/lib64/python3.7/json/encoder.py", line 431, in _iterencode
yield from _iterencode_dict(o, _current_indent_level)
File "/usr/lib64/python3.7/json/encoder.py", line 405, in _iterencode_dict
yield from chunks
File "/usr/lib64/python3.7/json/encoder.py", line 376, in _iterencode_dict
raise TypeError(f'keys must be str, int, float, bool or None, '
TypeError: keys must be str, int, float, bool or None, not tuple
```
| https://github.com/ansible/ansible/issues/62096 | https://github.com/ansible/ansible/pull/62115 | 53aa258d78650317aae09328980801f9d338c0b5 | 6fb1d56fdc022cb6001539ea4bbc87d759093987 | 2019-09-10T19:41:03Z | python | 2019-09-11T05:12:38Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 62,083 | ["changelogs/fragments/62083-vmware-internal_results.yml", "docs/docsite/rst/porting_guides/porting_guide_2.10.rst", "lib/ansible/modules/cloud/vmware/vmware_datastore_maintenancemode.py", "lib/ansible/modules/cloud/vmware/vmware_host_kernel_manager.py", "lib/ansible/modules/cloud/vmware/vmware_host_ntp.py", "lib/ansible/modules/cloud/vmware/vmware_host_service_manager.py", "lib/ansible/modules/cloud/vmware/vmware_tag.py"] | VMware: Modules with internal 'results' key in module return | ##### SUMMARY
The following modules throw a `[WARNING]: Found internal 'results' key in module return, renamed to 'ansible_module_results'`:
* [ ] `vmware_datastore_maintenancemode`
* [ ] `vmware_host_kernel_manager`
* [ ] `vmware_host_ntp`
* [ ] `vmware_host_service_manager`
* [ ] `vmware_tag`
I've generated the list like this:
`cd lib/ansible/modules/cloud/vmware/ && grep exit_json *.py | grep results= | cut -d ':' -f 1 | cut -d '.' -f 1`
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
vmware
##### ANSIBLE VERSION
`devel` | https://github.com/ansible/ansible/issues/62083 | https://github.com/ansible/ansible/pull/62161 | 041c52d629a47e34f755f6c765c213b3a7b896e1 | 1c3effe92e747eb4eef8021032a9ed8321655a97 | 2019-09-10T16:57:53Z | python | 2019-09-13T04:27:04Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 62,079 | ["changelogs/fragments/ansible-test-collection-identifier.yml", "test/lib/ansible_test/_internal/data.py", "test/lib/ansible_test/_internal/provider/layout/collection.py", "test/lib/ansible_test/_internal/util.py"] | collections sanity tests should start by verifying its a valid collection |
currently an invalid collection will error out on docs sanity, but this is misleading since the problem is that the collection name itself is invalid, a previous test verifying this should be introduced to avoid confusion.
example currently:
```
Running sanity test 'ansible-doc' with Python 3.7
ERROR: Command "ansible-doc -t module cyberark.ansible-security-automation-collection.cyberark_account cyberark.ansible-security-automation-collection.cyberark_authentication cyberark.ansible-security-automation-collection.cyberark_credential cyberark.ansible-security-automation-collection.cyberark_user" returned exit status 250.
>>> Standard Error
[WARNING]: module cyberark.ansible-security-automation-collection.cyberark_account not found in: /dev/null:/home/abehl/work/src/anshul_ansible/ansible/lib/ansible/modules
ERROR! Unexpected Exception, this is probably a bug: cannot unpack non-iterable NoneType object
```
##### ISSUE TYPE
- Feature Idea
##### COMPONENT NAME
<!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure -->
ansible-test
| https://github.com/ansible/ansible/issues/62079 | https://github.com/ansible/ansible/pull/76869 | de5f60e374524de13fe079b52282cd7a9eeabd5f | 26b43f425f6c04732818f600e1cf4bcb9a56f89a | 2019-09-10T16:03:06Z | python | 2022-01-28T01:24:40Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 62,075 | ["changelogs/fragments/ansible-test-ignore-tests-output.yml", "test/lib/ansible_test/_internal/provider/source/unversioned.py"] | ansible-test sanity on collections should ignore tests/output directory | <!--- Verify first that your issue is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
<!--- Explain the problem briefly below -->
ansible-test sanity also checks the automatically created tests/output directory and is failing the symlink test. This happens when running ansible-sanity on collection
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
<!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure -->
ansible-test
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
Stable 2.9
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
Running ansible-test sanity on a collection with python 3.7
<!--- Paste example playbooks or commands between quotes below -->
```yaml
```
<!--- HINT: You can paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
Ignore the tests/output directory
##### ACTUAL RESULTS
<!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) -->
<!--- Paste verbatim command output between quotes -->
```paste below
Running sanity test 'symlinks' with Python 3.7
ERROR: Found 6 symlinks issue(s) which need to be resolved:
ERROR: tests/output/.tmp/sanity/import/lib/ansible/module_utils:0:0: symlinks outside content tree are not allowed: ../../../../../../../../../../anshul_ansible/ansible/lib/ansible/module_utils
ERROR: tests/output/.tmp/sanity/import/lib/ansible/utils/collection_loader.py:0:0: symlinks outside content tree are not allowed: ../../../../../../../../../../../anshul_ansible/ansible/lib/ansible/utils/collection_loader.py
ERROR: tests/output/.tmp/sanity/import/lib/ansible/utils/singleton.py:0:0: symlinks outside content tree are not allowed: ../../../../../../../../../../../anshul_ansible/ansible/lib/ansible/utils/singleton.py
ERROR: tests/output/.tmp/sanity/import/minimal-py37/bin/importer.py:0:0: symlinks outside content tree are not allowed: ../../../../../../../../../../anshul_ansible/ansible/test/lib/ansible_test/_data/sanity/import/importer.py
ERROR: tests/output/.tmp/sanity/import/minimal-py37/bin/python:0:0: symlinks outside content tree are not allowed: ../../../../../../../../../../anshul_ansible/ansible/venv3/bin/python3
ERROR: tests/output/.tmp/sanity/import/minimal-py37/bin/python3:0:0: symlinks outside content tree are not allowed: ../../../../../../../../../../anshul_ansible/ansible/venv3/bin/python3
```
| https://github.com/ansible/ansible/issues/62075 | https://github.com/ansible/ansible/pull/62084 | 0f52b18f3f42626ac1499a49d4a58c78d1a1ab32 | f110abb8061fe6a629e12c782cef32ae2d3152e9 | 2019-09-10T15:32:16Z | python | 2019-09-10T22:49:40Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 62,052 | ["changelogs/fragments/62329-nsupdate-lookup-internal-zones.yaml", "lib/ansible/modules/net_tools/nsupdate.py"] | [nsupdate] : please use the server parameter in dns.resolver.zone_for_name | ##### SUMMARY
server parameter is required but not used as for zone resolution.
##### ISSUE TYPE
dns.resolver.zone_for_name is using system resolver so it can't be used to manage DNS entries from an external DNS without zone parameter. Zone resolution fails in this case.
The server parameter should be used as resolver.
##### COMPONENT NAME
nsupdate
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```ansible 2.7.5
config file = /home/sylvain/.ansible.cfg
configured module search path = [u'/usr/local/share/ansible']
ansible python module location = /usr/lib/python2.7/dist-packages/ansible
executable location = /usr/bin/ansible
python version = 2.7.13 (default, Sep 26 2018, 18:42:22) [GCC 6.3.0 20170516]
```
##### CONFIGURATION
```
ANSIBLE_PIPELINING(/home/user/.ansible.cfg) = True
ANSIBLE_SSH_ARGS(/home/user/.ansible.cfg) = -o ControlMaster=auto -o ControlPersist=60m
ANSIBLE_SSH_CONTROL_PATH(/home/user/.ansible.cfg) = ~/.ssh/master-%%C
ANY_ERRORS_FATAL(/home/user/.ansible.cfg) = True
COLOR_DIFF_ADD(/home/user/.ansible.cfg) = yellow
COLOR_DIFF_LINES(/home/user/.ansible.cfg) = yellow
COLOR_DIFF_REMOVE(/home/user/.ansible.cfg) = yellow
DEFAULT_GATHERING(/home/user/.ansible.cfg) = smart
DEFAULT_GATHER_SUBSET(/home/user/.ansible.cfg) = min,network,hardware
DEFAULT_JINJA2_EXTENSIONS(/home/user/.ansible.cfg) = jinja2.ext.do
DEFAULT_SCP_IF_SSH(/home/user/.ansible.cfg) = True
DEFAULT_STDOUT_CALLBACK(/home/user/.ansible.cfg) = debug
DEFAULT_TIMEOUT(/home/user/.ansible.cfg) = 30
DIFF_ALWAYS(/home/user/.ansible.cfg) = True
INJECT_FACTS_AS_VARS(/home/user/.ansible.cfg) = False
INVENTORY_IGNORE_EXTS(/home/user/.ansible.cfg) = [u'.pyc', u'.pyo', u'.swp', u'.bak', u'.md', u'.txt', u'~', u'.orig', u'.ini', u'.cfg', u'.retry', u'.old', u'.dpkg-old', u'.dpkg-new']
PERSISTENT_CONTROL_PATH_DIR(/home/user/.ansible.cfg) = /home/user/.ansible/pc
RETRY_FILES_ENABLED(/home/user/.ansible.cfg) = False
```
##### OS / ENVIRONMENT
Debian 9.9
##### STEPS TO REPRODUCE
```
- name: PTR entry
nsupdate:
key_name: "nsupdate"
key_secret: "+bFQtBCta7j2vWkjPkAFtgA=="
server: "10.0.0.1"
record: "4.0.31.172.in-addr.arpa."
type: "PTR"
value: "server1.local."
```
This task failed :
##### EXPECTED RESULTS
Zone resolver should use server parameter : 10.0.0.1.
##### ACTUAL RESULTS
Exit with this error
```
Zone resolver error (NoNameservers): All nameservers failed to answer the query 4.0.31.172.in-addr.arpa. IN SOA: Server 127.0.0.1 UDP port 53 answered SERVFAIL
```
| https://github.com/ansible/ansible/issues/62052 | https://github.com/ansible/ansible/pull/62329 | ee91714eb2c4f65862a227f9ced9c7b656265a0f | 75dfe6c88aee21b26e86b0aa03dacb07b627c80e | 2019-09-10T10:17:03Z | python | 2019-09-28T17:34:28Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,985 | ["changelogs/fragments/65051-regex-replace-multiline.yaml", "docs/docsite/rst/user_guide/playbooks_filters.rst", "lib/ansible/plugins/filter/core.py", "test/integration/targets/filter_core/files/foo.txt", "test/integration/targets/filter_core/templates/foo.j2"] | Multiline support for the regex_replace filter | ##### SUMMARY
I think the `regex_replace` jinja filter should support `multiline` as the `regex_search` do.
Or maybe use a `flags` parameter to support any `re` flag.
##### ISSUE TYPE
- Feature Idea
##### COMPONENT NAME
- `lib/ansible/plugins/filter/core.py`
##### ADDITIONAL INFORMATION
Example: comment a multiline variable.
```yaml
val: "{{ val | regex_replace('^', '#', multiline=True) }}"
``` | https://github.com/ansible/ansible/issues/61985 | https://github.com/ansible/ansible/pull/65051 | b3db41e6d8d8fe0b2d559a35ab2a4557b26c56a8 | e867535a5700ab5cc38e57593e24926bb3f4b903 | 2019-09-09T09:57:21Z | python | 2020-02-19T17:19:40Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,983 | ["changelogs/fragments/find-contains-docs.yaml", "lib/ansible/modules/files/find.py"] | find_module: contains attribute ambiguously described | <!--- Verify first that your improvement is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
<!--- Explain the problem briefly below, add suggestions to wording or structure -->
The contains attribute of the find_module has type "string" but is described as "one or more regex patterns". Given that a string can only be one regex pattern (albeit with alternations in it to match against multiple patterns) it is deceptively easy to misread this and try to specify a list of strings as the value of the contains attribute.
Granted, Ansible warns about this when running, but it would be even better to prevent the mistake in the first place.
<!--- HINT: Did you know the documentation has an "Edit on GitHub" link on every page ? -->
I would edit the documentation myself, but I don't actually know what the intended semantics for this are. Is the command meant to take a list of regexes? If so, the bug is that it doesn't. If it's only meant to take a single regex, the bug is in the description in the documentation!
##### ISSUE TYPE
- Documentation Report
##### COMPONENT NAME
<!--- Write the short name of the rst file, module, plugin, task or feature below, use your best guess if unsure -->
find_module
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
ansible 2.8.4
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
DEFAULT_VAULT_PASSWORD_FILE(env: ANSIBLE_VAULT_PASSWORD_FILE) = /home/kqr/.vaultpass
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. OS version, browser, etc. -->
All (documentation published on the web)
##### ADDITIONAL INFORMATION
<!--- Describe how this improves the documentation, e.g. before/after situation or screenshots -->
<!--- HINT: You can paste gist.github.com links for larger files -->
| https://github.com/ansible/ansible/issues/61983 | https://github.com/ansible/ansible/pull/62445 | d4064a965b0fcba974c85bb49991f28ddf00cba4 | 2375fd099035fadb781c7bfdb8bc8ce18b5e0601 | 2019-09-09T09:17:21Z | python | 2019-09-26T15:33:14Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,976 | ["lib/ansible/modules/windows/win_group.ps1"] | win_group doesn't support check mode | <!--- Verify first that your issue is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
Support for running in check mode was added to `win_group` way back in #21384, but the flag was never enabled so the engine skips the entire module anyway.
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
<!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure -->
win_group
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
ansible 2.5.3
config file = /etc/ansible/ansible.cfg
configured module search path = [u'/usr/share/ansible']
ansible python module location = /usr/local/lib/python2.7/dist-packages/ansible
executable location = /usr/local/bin/ansible
python version = 2.7.12 (default, Dec 4 2017, 14:50:18) [GCC 5.4.0 20160609]
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
DEFAULT_CALLBACK_WHITELIST(/etc/ansible/ansible.cfg) = ['datadog_callback', 'profile_tasks']
DEFAULT_FORKS(/etc/ansible/ansible.cfg) = 15
DEFAULT_HOST_LIST(/etc/ansible/ansible.cfg) = [u'/etc/ansible/hosts']
DEFAULT_LOG_PATH(/etc/ansible/ansible.cfg) = /var/log/ansible.log
DEFAULT_MODULE_PATH(/etc/ansible/ansible.cfg) = [u'/usr/share/ansible']
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
<!--- Paste example playbooks or commands between quotes below -->
```yaml
- win_group:
name: my_gorup
check_mode: yes
```
<!--- HINT: You can paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
(normal output of what would or wouldn't have been changed)
##### ACTUAL RESULTS
<!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) -->
<!--- Paste verbatim command output between quotes -->
```paste below
skipping: [host] => {
"changed": false,
"msg": "remote module does not support check mode"
}
```
| https://github.com/ansible/ansible/issues/61976 | https://github.com/ansible/ansible/pull/61977 | a0bec0bc327d29f446a031abc803b8d2cad1949f | d361ff412282fe9b4c701aba85a7b4846a29ee21 | 2019-09-08T20:37:48Z | python | 2019-09-15T20:45:43Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,965 | ["changelogs/fragments/61965-user-module-fails-to-change-primary-group.yml", "lib/ansible/modules/user.py", "test/integration/targets/user/tasks/test_local.yml"] | user module fails to change primary group | <!--- Verify first that your issue is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
running `ansible -m "user" -a "name=pihole state=present group=docker local=yes"` fails with `Invalid group ID docker\nUsage: lusermod `...
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
user
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```
ansible 2.8.3
config file = /etc/ansible/ansible.cfg
configured module search path = [u'/home/administrator/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python2.7/dist-packages/ansible
executable location = /usr/bin/ansible
python version = 2.7.15+ (default, Nov 27 2018, 23:36:35) [GCC 7.3.0]
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```
ansible 2.8.3
config file = /etc/ansible/ansible.cfg
configured module search path = [u'/home/administrator/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python2.7/dist-packages/ansible
executable location = /usr/bin/ansible
python version = 2.7.15+ (default, Nov 27 2018, 23:36:35) [GCC 7.3.0]
```
##### OS / ENVIRONMENT
Ubuntu 18.04.03
##### STEPS TO REPRODUCE
Create two groups on the host `group1` and `group2`
Run `ansible -i "192.168.1.10," -bkK -m "user" -a "name=testuser state=present group=group1 local=yes" all` (or equivalent)
Then run ` ansible -i "192.168.1.10," -bkK -m "user" -a "name=testuser state=present group=group2 local=yes" all`
<!--- HINT: You can paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
The second command should succeed and change the user's primary group to group2
##### ACTUAL RESULTS
<!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) -->
It seems that for whatever reason ansible is calling lgroupmod with the group name, where it should be the group id (the module documentation asks for a group name).
The lusermod command on my system is installed via the package `libuser | 1:0.62~dfsg-0.1ubuntu2 | http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages`
<!--- Paste verbatim command output between quotes -->
```
ansible 2.8.3
config file = /etc/ansible/ansible.cfg
configured module search path = [u'/home/administrator/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python2.7/dist-packages/ansible
executable location = /usr/bin/ansible
python version = 2.7.15+ (default, Nov 27 2018, 23:36:35) [GCC 7.3.0]
Using /etc/ansible/ansible.cfg as config file
SSH password:
BECOME password[defaults to SSH password]:
setting up inventory plugins
Parsed 192.168.1.10, inventory source with host_list plugin
Loading callback plugin minimal of type stdout, v2.0 from /usr/lib/python2.7/dist-packages/ansible/plugins/callback/minimal.pyc
META: ran handlers
<192.168.1.10> ESTABLISH SSH CONNECTION FOR USER: None
<192.168.1.10> SSH: EXEC sshpass -d10 ssh -vvv -C -o ControlMaster=auto -o ControlPersist=60s -o ConnectTimeout=60 -o ControlPath=/home/administrator/.ansible/cp/0b3ee26c83 192.168.1.10 '/bin/sh -c '"'"'echo ~ && sleep 0'"'"''
<192.168.1.10> (0, '/home/administrator\n', 'OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017\r\ndebug1: Reading configuration data /etc/ssh/ssh_config\r\ndebug1: /etc/ssh/ssh_config line 19: Applying options for *\r\ndebug1: auto-mux: Trying existing master\r\ndebug1: Control socket "/home/administrator/.ansible/cp/0b3ee26c83" does not exist\r\ndebug2: resolving "192.168.1.10" port 22\r\ndebug2: ssh_connect_direct: needpriv 0\r\ndebug1: Connecting to 192.168.1.10 [192.168.1.10] port 22.\r\ndebug2: fd 3 setting O_NONBLOCK\r\ndebug1: fd 3 clearing O_NONBLOCK\r\ndebug1: Connection established.\r\ndebug3: timeout: 59987 ms remain after connect\r\ndebug1: key_load_public: No such file or directory\r\ndebug1: identity file /home/administrator/.ssh/id_rsa type -1\r\ndebug1: key_load_public: No such file or directory\r\ndebug1: identity file /home/administrator/.ssh/id_rsa-cert type -1\r\ndebug1: key_load_public: No such file or directory\r\ndebug1: identity file /home/administrator/.ssh/id_dsa type -1\r\ndebug1: key_load_public: No such file or directory\r\ndebug1: identity file /home/administrator/.ssh/id_dsa-cert type -1\r\ndebug1: key_load_public: No such file or directory\r\ndebug1: identity file /home/administrator/.ssh/id_ecdsa type -1\r\ndebug1: key_load_public: No such file or directory\r\ndebug1: identity file /home/administrator/.ssh/id_ecdsa-cert type -1\r\ndebug1: key_load_public: No such file or directory\r\ndebug1: identity file /home/administrator/.ssh/id_ed25519 type -1\r\ndebug1: key_load_public: No such file or directory\r\ndebug1: identity file /home/administrator/.ssh/id_ed25519-cert type -1\r\ndebug1: Local version string SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3\r\ndebug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 Ubuntu-4ubuntu0.3\r\ndebug1: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 pat OpenSSH* compat 0x04000000\r\ndebug2: fd 3 setting O_NONBLOCK\r\ndebug1: Authenticating to 192.168.1.10:22 as \'administrator\'\r\ndebug3: hostkeys_foreach: reading file "/home/administrator/.ssh/known_hosts"\r\ndebug3: record_hostkey: found key type ECDSA in file /home/administrator/.ssh/known_hosts:15\r\ndebug3: load_hostkeys: loaded 1 keys from 192.168.1.10\r\ndebug3: order_hostkeyalgs: prefer hostkeyalgs: [email protected],[email protected],[email protected],ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521\r\ndebug3: send packet: type 20\r\ndebug1: SSH2_MSG_KEXINIT sent\r\ndebug3: receive packet: type 20\r\ndebug1: SSH2_MSG_KEXINIT received\r\ndebug2: local client KEXINIT proposal\r\ndebug2: KEX algorithms: curve25519-sha256,[email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1,ext-info-c\r\ndebug2: host key algorithms: [email protected],[email protected],[email protected],ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,[email protected],[email protected],ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa\r\ndebug2: ciphers ctos: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected]\r\ndebug2: ciphers stoc: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected]\r\ndebug2: MACs ctos: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1\r\ndebug2: MACs stoc: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1\r\ndebug2: compression ctos: [email protected],zlib,none\r\ndebug2: compression stoc: [email protected],zlib,none\r\ndebug2: languages ctos: \r\ndebug2: languages stoc: \r\ndebug2: first_kex_follows 0 \r\ndebug2: reserved 0 \r\ndebug2: peer server KEXINIT proposal\r\ndebug2: KEX algorithms: curve25519-sha256,[email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1\r\ndebug2: host key algorithms: ssh-rsa,rsa-sha2-512,rsa-sha2-256,ecdsa-sha2-nistp256,ssh-ed25519\r\ndebug2: ciphers ctos: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected]\r\ndebug2: ciphers stoc: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected]\r\ndebug2: MACs ctos: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1\r\ndebug2: MACs stoc: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1\r\ndebug2: compression ctos: none,[email protected]\r\ndebug2: compression stoc: none,[email protected]\r\ndebug2: languages ctos: \r\ndebug2: languages stoc: \r\ndebug2: first_kex_follows 0 \r\ndebug2: reserved 0 \r\ndebug1: kex: algorithm: curve25519-sha256\r\ndebug1: kex: host key algorithm: ecdsa-sha2-nistp256\r\ndebug1: kex: server->client cipher: [email protected] MAC: <implicit> compression: [email protected]\r\ndebug1: kex: client->server cipher: [email protected] MAC: <implicit> compression: [email protected]\r\ndebug3: send packet: type 30\r\ndebug1: expecting SSH2_MSG_KEX_ECDH_REPLY\r\ndebug3: receive packet: type 31\r\ndebug1: Server host key: ecdsa-sha2-nistp256 SHA256:EJTV6fte0d8PlFrl1jC2AbeoXLx48usCs8mpg3AgDmA\r\ndebug3: hostkeys_foreach: reading file "/home/administrator/.ssh/known_hosts"\r\ndebug3: record_hostkey: found key type ECDSA in file /home/administrator/.ssh/known_hosts:15\r\ndebug3: load_hostkeys: loaded 1 keys from 192.168.1.10\r\ndebug1: Host \'192.168.1.10\' is known and matches the ECDSA host key.\r\ndebug1: Found key in /home/administrator/.ssh/known_hosts:15\r\ndebug3: send packet: type 21\r\ndebug2: set_newkeys: mode 1\r\ndebug1: rekey after 134217728 blocks\r\ndebug1: SSH2_MSG_NEWKEYS sent\r\ndebug1: expecting SSH2_MSG_NEWKEYS\r\ndebug3: receive packet: type 21\r\ndebug1: SSH2_MSG_NEWKEYS received\r\ndebug2: set_newkeys: mode 0\r\ndebug1: rekey after 134217728 blocks\r\ndebug2: key: /home/administrator/.ssh/id_rsa ((nil))\r\ndebug2: key: /home/administrator/.ssh/id_dsa ((nil))\r\ndebug2: key: /home/administrator/.ssh/id_ecdsa ((nil))\r\ndebug2: key: /home/administrator/.ssh/id_ed25519 ((nil))\r\ndebug3: send packet: type 5\r\ndebug3: receive packet: type 7\r\ndebug1: SSH2_MSG_EXT_INFO received\r\ndebug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521>\r\ndebug3: receive packet: type 6\r\ndebug2: service_accept: ssh-userauth\r\ndebug1: SSH2_MSG_SERVICE_ACCEPT received\r\ndebug3: send packet: type 50\r\ndebug3: receive packet: type 51\r\ndebug1: Authentications that can continue: publickey,password\r\ndebug3: start over, passed a different list publickey,password\r\ndebug3: preferred gssapi-keyex,gssapi-with-mic,publickey,keyboard-interactive,password\r\ndebug3: authmethod_lookup publickey\r\ndebug3: remaining preferred: keyboard-interactive,password\r\ndebug3: authmethod_is_enabled publickey\r\ndebug1: Next authentication method: publickey\r\ndebug1: Trying private key: /home/administrator/.ssh/id_rsa\r\ndebug3: no such identity: /home/administrator/.ssh/id_rsa: No such file or directory\r\ndebug1: Trying private key: /home/administrator/.ssh/id_dsa\r\ndebug3: no such identity: /home/administrator/.ssh/id_dsa: No such file or directory\r\ndebug1: Trying private key: /home/administrator/.ssh/id_ecdsa\r\ndebug3: no such identity: /home/administrator/.ssh/id_ecdsa: No such file or directory\r\ndebug1: Trying private key: /home/administrator/.ssh/id_ed25519\r\ndebug3: no such identity: /home/administrator/.ssh/id_ed25519: No such file or directory\r\ndebug2: we did not send a packet, disable method\r\ndebug3: authmethod_lookup password\r\ndebug3: remaining preferred: ,password\r\ndebug3: authmethod_is_enabled password\r\ndebug1: Next authentication method: password\r\ndebug3: send packet: type 50\r\ndebug2: we sent a password packet, wait for reply\r\ndebug3: receive packet: type 52\r\ndebug1: Enabling compression at level 6.\r\ndebug1: Authentication succeeded (password).\r\nAuthenticated to 192.168.1.10 ([192.168.1.10]:22).\r\ndebug1: setting up multiplex master socket\r\ndebug3: muxserver_listen: temporary control path /home/administrator/.ansible/cp/0b3ee26c83.baLkbl796Za3h1Bh\r\ndebug2: fd 4 setting O_NONBLOCK\r\ndebug3: fd 4 is O_NONBLOCK\r\ndebug3: fd 4 is O_NONBLOCK\r\ndebug1: channel 0: new [/home/administrator/.ansible/cp/0b3ee26c83]\r\ndebug3: muxserver_listen: mux listener channel 0 fd 4\r\ndebug2: fd 3 setting TCP_NODELAY\r\ndebug3: ssh_packet_set_tos: set IP_TOS 0x08\r\ndebug1: control_persist_detach: backgrounding master process\r\ndebug2: control_persist_detach: background process is 10510\r\ndebug2: fd 4 setting O_NONBLOCK\r\ndebug1: forking to background\r\ndebug1: Entering interactive session.\r\ndebug1: pledge: id\r\ndebug2: set_control_persist_exit_time: schedule exit in 60 seconds\r\ndebug1: multiplexing control connection\r\ndebug2: fd 5 setting O_NONBLOCK\r\ndebug3: fd 5 is O_NONBLOCK\r\ndebug1: channel 1: new [mux-control]\r\ndebug3: channel_post_mux_listener: new mux channel 1 fd 5\r\ndebug3: mux_master_read_cb: channel 1: hello sent\r\ndebug2: set_control_persist_exit_time: cancel scheduled exit\r\ndebug3: mux_master_read_cb: channel 1 packet type 0x00000001 len 4\r\ndebug2: process_mux_master_hello: channel 1 slave version 4\r\ndebug2: mux_client_hello_exchange: master version 4\r\ndebug3: mux_client_forwards: request forwardings: 0 local, 0 remote\r\ndebug3: mux_client_request_session: entering\r\ndebug3: mux_client_request_alive: entering\r\ndebug3: mux_master_read_cb: channel 1 packet type 0x10000004 len 4\r\ndebug2: process_mux_alive_check: channel 1: alive check\r\ndebug3: mux_client_request_alive: done pid = 10512\r\ndebug3: mux_client_request_session: session request sent\r\ndebug3: mux_master_read_cb: channel 1 packet type 0x10000002 len 91\r\ndebug2: process_mux_new_session: channel 1: request tty 0, X 0, agent 0, subsys 0, term "xterm", cmd "/bin/sh -c \'echo ~ && sleep 0\'", env 1\r\ndebug3: process_mux_new_session: got fds stdin 6, stdout 7, stderr 8\r\ndebug2: fd 7 setting O_NONBLOCK\r\ndebug2: fd 8 setting O_NONBLOCK\r\ndebug1: channel 2: new [client-session]\r\ndebug2: process_mux_new_session: channel_new: 2 linked to control channel 1\r\ndebug2: channel 2: send open\r\ndebug3: send packet: type 90\r\ndebug3: receive packet: type 80\r\ndebug1: client_input_global_request: rtype [email protected] want_reply 0\r\ndebug3: receive packet: type 91\r\ndebug2: channel_input_open_confirmation: channel 2: callback start\r\ndebug2: client_session2_setup: id 2\r\ndebug1: Sending environment.\r\ndebug1: Sending env LANG = en_US.UTF-8\r\ndebug2: channel 2: request env confirm 0\r\ndebug3: send packet: type 98\r\ndebug1: Sending command: /bin/sh -c \'echo ~ && sleep 0\'\r\ndebug2: channel 2: request exec confirm 1\r\ndebug3: send packet: type 98\r\ndebug3: mux_session_confirm: sending success reply\r\ndebug2: channel_input_open_confirmation: channel 2: callback done\r\ndebug2: channel 2: open confirm rwindow 0 rmax 32768\r\ndebug1: mux_client_request_session: master session id: 2\r\ndebug2: channel 2: rcvd adjust 2097152\r\ndebug3: receive packet: type 99\r\ndebug2: channel_input_status_confirm: type 99 id 2\r\ndebug2: exec request accepted on channel 2\r\ndebug3: receive packet: type 98\r\ndebug1: client_input_channel_req: channel 2 rtype exit-status reply 0\r\ndebug3: mux_exit_message: channel 2: exit message, exitval 0\r\ndebug3: receive packet: type 98\r\ndebug1: client_input_channel_req: channel 2 rtype [email protected] reply 0\r\ndebug2: channel 2: rcvd eow\r\ndebug2: channel 2: close_read\r\ndebug2: channel 2: input open -> closed\r\ndebug3: receive packet: type 96\r\ndebug2: channel 2: rcvd eof\r\ndebug2: channel 2: output open -> drain\r\ndebug2: channel 2: obuf empty\r\ndebug2: channel 2: close_write\r\ndebug2: channel 2: output drain -> closed\r\ndebug3: receive packet: type 97\r\ndebug2: channel 2: rcvd close\r\ndebug3: channel 2: will not send data after close\r\ndebug2: channel 2: send close\r\ndebug3: send packet: type 97\r\ndebug2: channel 2: is dead\r\ndebug2: channel 2: gc: notify user\r\ndebug3: mux_master_session_cleanup_cb: entering for channel 2\r\ndebug2: channel 1: rcvd close\r\ndebug2: channel 1: output open -> drain\r\ndebug2: channel 1: close_read\r\ndebug2: channel 1: input open -> closed\r\ndebug2: channel 2: gc: user detached\r\ndebug2: channel 2: is dead\r\ndebug2: channel 2: garbage collecting\r\ndebug1: channel 2: free: client-session, nchannels 3\r\ndebug3: channel 2: status: The following connections are open:\r\n #1 mux-control (t16 nr0 i3/0 o1/16 fd 5/5 cc -1)\r\n #2 client-session (t4 r0 i3/0 o3/0 fd -1/-1 cc -1)\r\n\r\ndebug2: channel 1: obuf empty\r\ndebug2: channel 1: close_write\r\ndebug2: channel 1: output drain -> closed\r\ndebug2: channel 1: is dead (local)\r\ndebug2: channel 1: gc: notify user\r\ndebug3: mux_master_control_cleanup_cb: entering for channel 1\r\ndebug2: channel 1: gc: user detached\r\ndebug2: channel 1: is dead (local)\r\ndebug2: channel 1: garbage collecting\r\ndebug1: channel 1: free: mux-control, nchannels 2\r\ndebug3: mux_client_read_packet: read header failed: Broken pipe\r\ndebug3: channel 1: status: The following connections are open:\r\n #1 mux-control (t16 nr0 i3/0 o3/0 fd 5/5 cc -1)\r\n\r\ndebug2: Received exit status from master 0\r\ndebug2: set_control_persist_exit_time: schedule exit in 60 seconds\r\n')
<192.168.1.10> ESTABLISH SSH CONNECTION FOR USER: None
<192.168.1.10> SSH: EXEC sshpass -d10 ssh -vvv -C -o ControlMaster=auto -o ControlPersist=60s -o ConnectTimeout=60 -o ControlPath=/home/administrator/.ansible/cp/0b3ee26c83 192.168.1.10 '/bin/sh -c '"'"'( umask 77 && mkdir -p "` echo /home/administrator/.ansible/tmp/ansible-tmp-1567895066.22-102865223087764 `" && echo ansible-tmp-1567895066.22-102865223087764="` echo /home/administrator/.ansible/tmp/ansible-tmp-1567895066.22-102865223087764 `" ) && sleep 0'"'"''
<192.168.1.10> (0, 'ansible-tmp-1567895066.22-102865223087764=/home/administrator/.ansible/tmp/ansible-tmp-1567895066.22-102865223087764\n', 'OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017\r\ndebug1: Reading configuration data /etc/ssh/ssh_config\r\ndebug1: /etc/ssh/ssh_config line 19: Applying options for *\r\ndebug1: auto-mux: Trying existing master\r\ndebug2: fd 3 setting O_NONBLOCK\r\ndebug2: mux_client_hello_exchange: master version 4\r\ndebug3: mux_client_forwards: request forwardings: 0 local, 0 remote\r\ndebug3: mux_client_request_session: entering\r\ndebug3: mux_client_request_alive: entering\r\ndebug3: mux_client_request_alive: done pid = 10512\r\ndebug3: mux_client_request_session: session request sent\r\ndebug1: mux_client_request_session: master session id: 2\r\ndebug3: mux_client_read_packet: read header failed: Broken pipe\r\ndebug2: Received exit status from master 0\r\n')
<192.168.1.10> Attempting python interpreter discovery
<192.168.1.10> ESTABLISH SSH CONNECTION FOR USER: None
<192.168.1.10> SSH: EXEC sshpass -d10 ssh -vvv -C -o ControlMaster=auto -o ControlPersist=60s -o ConnectTimeout=60 -o ControlPath=/home/administrator/.ansible/cp/0b3ee26c83 192.168.1.10 '/bin/sh -c '"'"'echo PLATFORM; uname; echo FOUND; command -v '"'"'"'"'"'"'"'"'/usr/bin/python'"'"'"'"'"'"'"'"'; command -v '"'"'"'"'"'"'"'"'python3.7'"'"'"'"'"'"'"'"'; command -v '"'"'"'"'"'"'"'"'python3.6'"'"'"'"'"'"'"'"'; command -v '"'"'"'"'"'"'"'"'python3.5'"'"'"'"'"'"'"'"'; command -v '"'"'"'"'"'"'"'"'python2.7'"'"'"'"'"'"'"'"'; command -v '"'"'"'"'"'"'"'"'python2.6'"'"'"'"'"'"'"'"'; command -v '"'"'"'"'"'"'"'"'/usr/libexec/platform-python'"'"'"'"'"'"'"'"'; command -v '"'"'"'"'"'"'"'"'/usr/bin/python3'"'"'"'"'"'"'"'"'; command -v '"'"'"'"'"'"'"'"'python'"'"'"'"'"'"'"'"'; echo ENDFOUND && sleep 0'"'"''
<192.168.1.10> (0, 'PLATFORM\nLinux\nFOUND\n/usr/bin/python\n/usr/bin/python3.6\n/usr/bin/python2.7\n/usr/bin/python3\n/usr/bin/python\nENDFOUND\n', 'OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017\r\ndebug1: Reading configuration data /etc/ssh/ssh_config\r\ndebug1: /etc/ssh/ssh_config line 19: Applying options for *\r\ndebug1: auto-mux: Trying existing master\r\ndebug2: fd 3 setting O_NONBLOCK\r\ndebug2: mux_client_hello_exchange: master version 4\r\ndebug3: mux_client_forwards: request forwardings: 0 local, 0 remote\r\ndebug3: mux_client_request_session: entering\r\ndebug3: mux_client_request_alive: entering\r\ndebug3: mux_client_request_alive: done pid = 10512\r\ndebug3: mux_client_request_session: session request sent\r\ndebug1: mux_client_request_session: master session id: 2\r\ndebug3: mux_client_read_packet: read header failed: Broken pipe\r\ndebug2: Received exit status from master 0\r\n')
<192.168.1.10> ESTABLISH SSH CONNECTION FOR USER: None
<192.168.1.10> SSH: EXEC sshpass -d10 ssh -vvv -C -o ControlMaster=auto -o ControlPersist=60s -o ConnectTimeout=60 -o ControlPath=/home/administrator/.ansible/cp/0b3ee26c83 192.168.1.10 '/bin/sh -c '"'"'/usr/bin/python && sleep 0'"'"''
<192.168.1.10> (0, '{"osrelease_content": "NAME=\\"Ubuntu\\"\\nVERSION=\\"18.04.3 LTS (Bionic Beaver)\\"\\nID=ubuntu\\nID_LIKE=debian\\nPRETTY_NAME=\\"Ubuntu 18.04.3 LTS\\"\\nVERSION_ID=\\"18.04\\"\\nHOME_URL=\\"https://www.ubuntu.com/\\"\\nSUPPORT_URL=\\"https://help.ubuntu.com/\\"\\nBUG_REPORT_URL=\\"https://bugs.launchpad.net/ubuntu/\\"\\nPRIVACY_POLICY_URL=\\"https://www.ubuntu.com/legal/terms-and-policies/privacy-policy\\"\\nVERSION_CODENAME=bionic\\nUBUNTU_CODENAME=bionic\\n", "platform_dist_result": ["Ubuntu", "18.04", "bionic"]}\n', 'OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017\r\ndebug1: Reading configuration data /etc/ssh/ssh_config\r\ndebug1: /etc/ssh/ssh_config line 19: Applying options for *\r\ndebug1: auto-mux: Trying existing master\r\ndebug2: fd 3 setting O_NONBLOCK\r\ndebug2: mux_client_hello_exchange: master version 4\r\ndebug3: mux_client_forwards: request forwardings: 0 local, 0 remote\r\ndebug3: mux_client_request_session: entering\r\ndebug3: mux_client_request_alive: entering\r\ndebug3: mux_client_request_alive: done pid = 10512\r\ndebug3: mux_client_request_session: session request sent\r\ndebug1: mux_client_request_session: master session id: 2\r\ndebug3: mux_client_read_packet: read header failed: Broken pipe\r\ndebug2: Received exit status from master 0\r\n')
Using module file /usr/lib/python2.7/dist-packages/ansible/modules/system/user.py
<192.168.1.10> PUT /home/administrator/.ansible/tmp/ansible-local-10484Kwu1Jq/tmpW9YP7C TO /home/administrator/.ansible/tmp/ansible-tmp-1567895066.22-102865223087764/AnsiballZ_user.py
<192.168.1.10> SSH: EXEC sshpass -d10 sftp -o BatchMode=no -b - -vvv -C -o ControlMaster=auto -o ControlPersist=60s -o ConnectTimeout=60 -o ControlPath=/home/administrator/.ansible/cp/0b3ee26c83 '[192.168.1.10]'
<192.168.1.10> (0, 'sftp> put /home/administrator/.ansible/tmp/ansible-local-10484Kwu1Jq/tmpW9YP7C /home/administrator/.ansible/tmp/ansible-tmp-1567895066.22-102865223087764/AnsiballZ_user.py\n', 'OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017\r\ndebug1: Reading configuration data /etc/ssh/ssh_config\r\ndebug1: /etc/ssh/ssh_config line 19: Applying options for *\r\ndebug1: auto-mux: Trying existing master\r\ndebug2: fd 3 setting O_NONBLOCK\r\ndebug2: mux_client_hello_exchange: master version 4\r\ndebug3: mux_client_forwards: request forwardings: 0 local, 0 remote\r\ndebug3: mux_client_request_session: entering\r\ndebug3: mux_client_request_alive: entering\r\ndebug3: mux_client_request_alive: done pid = 10512\r\ndebug3: mux_client_request_session: session request sent\r\ndebug1: mux_client_request_session: master session id: 2\r\ndebug2: Remote version: 3\r\ndebug2: Server supports extension "[email protected]" revision 1\r\ndebug2: Server supports extension "[email protected]" revision 2\r\ndebug2: Server supports extension "[email protected]" revision 2\r\ndebug2: Server supports extension "[email protected]" revision 1\r\ndebug2: Server supports extension "[email protected]" revision 1\r\ndebug3: Sent message fd 5 T:16 I:1\r\ndebug3: SSH_FXP_REALPATH . -> /home/administrator size 0\r\ndebug3: Looking up /home/administrator/.ansible/tmp/ansible-local-10484Kwu1Jq/tmpW9YP7C\r\ndebug3: Sent message fd 5 T:17 I:2\r\ndebug3: Received stat reply T:101 I:2\r\ndebug1: Couldn\'t stat remote file: No such file or directory\r\ndebug3: Sent message SSH2_FXP_OPEN I:3 P:/home/administrator/.ansible/tmp/ansible-tmp-1567895066.22-102865223087764/AnsiballZ_user.py\r\ndebug3: Sent message SSH2_FXP_WRITE I:4 O:0 S:32768\r\ndebug3: SSH2_FXP_STATUS 0\r\ndebug3: In write loop, ack for 4 32768 bytes at 0\r\ndebug3: Sent message SSH2_FXP_WRITE I:5 O:32768 S:32768\r\ndebug3: Sent message SSH2_FXP_WRITE I:6 O:65536 S:32768\r\ndebug3: Sent message SSH2_FXP_WRITE I:7 O:98304 S:26837\r\ndebug3: SSH2_FXP_STATUS 0\r\ndebug3: In write loop, ack for 5 32768 bytes at 32768\r\ndebug3: SSH2_FXP_STATUS 0\r\ndebug3: In write loop, ack for 6 32768 bytes at 65536\r\ndebug3: SSH2_FXP_STATUS 0\r\ndebug3: In write loop, ack for 7 26837 bytes at 98304\r\ndebug3: Sent message SSH2_FXP_CLOSE I:4\r\ndebug3: SSH2_FXP_STATUS 0\r\ndebug3: mux_client_read_packet: read header failed: Broken pipe\r\ndebug2: Received exit status from master 0\r\n')
<192.168.1.10> ESTABLISH SSH CONNECTION FOR USER: None
<192.168.1.10> SSH: EXEC sshpass -d10 ssh -vvv -C -o ControlMaster=auto -o ControlPersist=60s -o ConnectTimeout=60 -o ControlPath=/home/administrator/.ansible/cp/0b3ee26c83 192.168.1.10 '/bin/sh -c '"'"'chmod u+x /home/administrator/.ansible/tmp/ansible-tmp-1567895066.22-102865223087764/ /home/administrator/.ansible/tmp/ansible-tmp-1567895066.22-102865223087764/AnsiballZ_user.py && sleep 0'"'"''
<192.168.1.10> (0, '', 'OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017\r\ndebug1: Reading configuration data /etc/ssh/ssh_config\r\ndebug1: /etc/ssh/ssh_config line 19: Applying options for *\r\ndebug1: auto-mux: Trying existing master\r\ndebug2: fd 3 setting O_NONBLOCK\r\ndebug2: mux_client_hello_exchange: master version 4\r\ndebug3: mux_client_forwards: request forwardings: 0 local, 0 remote\r\ndebug3: mux_client_request_session: entering\r\ndebug3: mux_client_request_alive: entering\r\ndebug3: mux_client_request_alive: done pid = 10512\r\ndebug3: mux_client_request_session: session request sent\r\ndebug1: mux_client_request_session: master session id: 2\r\ndebug3: mux_client_read_packet: read header failed: Broken pipe\r\ndebug2: Received exit status from master 0\r\n')
<192.168.1.10> ESTABLISH SSH CONNECTION FOR USER: None
<192.168.1.10> SSH: EXEC sshpass -d10 ssh -vvv -C -o ControlMaster=auto -o ControlPersist=60s -o ConnectTimeout=60 -o ControlPath=/home/administrator/.ansible/cp/0b3ee26c83 -tt 192.168.1.10 '/bin/sh -c '"'"'sudo -H -S -p "[sudo via ansible, key=sehkotddgkvdabyrauftxwzmpfnbqowz] password:" -u root /bin/sh -c '"'"'"'"'"'"'"'"'echo BECOME-SUCCESS-sehkotddgkvdabyrauftxwzmpfnbqowz ; /usr/bin/python /home/administrator/.ansible/tmp/ansible-tmp-1567895066.22-102865223087764/AnsiballZ_user.py'"'"'"'"'"'"'"'"' && sleep 0'"'"''
Escalation succeeded
<192.168.1.10> (1, '\r\n\r\n{"msg": "Group prigroup1 does not exist", "failed": true, "invocation": {"module_args": {"comment": null, "ssh_key_bits": 0, "update_password": "always", "non_unique": false, "force": false, "ssh_key_type": "rsa", "create_home": true, "password_lock": null, "ssh_key_passphrase": null, "uid": null, "home": null, "append": false, "skeleton": null, "ssh_key_comment": "ansible-generated on fserver2", "group": "prigroup1", "system": false, "state": "present", "role": null, "hidden": null, "local": true, "authorization": null, "profile": null, "shell": null, "expires": null, "ssh_key_file": null, "groups": null, "move_home": false, "password": null, "name": "testuser", "seuser": null, "remove": false, "login_class": null, "generate_ssh_key": null}}, "warnings": ["\'local: true\' specified and user was not found in /etc/passwd. The local user account may already exist if the local account database exists somewhere other than /etc/passwd.", "\'local: true\' specified and user was not found in /etc/passwd. The local user account may already exist if the local account database exists somewhere other than /etc/passwd.", "\'local: true\' specified and user was not found in /etc/passwd. The local user account may already exist if the local account database exists somewhere other than /etc/passwd."]}\r\n', 'OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017\r\ndebug1: Reading configuration data /etc/ssh/ssh_config\r\ndebug1: /etc/ssh/ssh_config line 19: Applying options for *\r\ndebug1: auto-mux: Trying existing master\r\ndebug2: fd 3 setting O_NONBLOCK\r\ndebug2: mux_client_hello_exchange: master version 4\r\ndebug3: mux_client_forwards: request forwardings: 0 local, 0 remote\r\ndebug3: mux_client_request_session: entering\r\ndebug3: mux_client_request_alive: entering\r\ndebug3: mux_client_request_alive: done pid = 10512\r\ndebug3: mux_client_request_session: session request sent\r\ndebug1: mux_client_request_session: master session id: 2\r\ndebug3: mux_client_read_packet: read header failed: Broken pipe\r\ndebug2: Received exit status from master 1\r\nShared connection to 192.168.1.10 closed.\r\n')
<192.168.1.10> Failed to connect to the host via ssh: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: auto-mux: Trying existing master
debug2: fd 3 setting O_NONBLOCK
debug2: mux_client_hello_exchange: master version 4
debug3: mux_client_forwards: request forwardings: 0 local, 0 remote
debug3: mux_client_request_session: entering
debug3: mux_client_request_alive: entering
debug3: mux_client_request_alive: done pid = 10512
debug3: mux_client_request_session: session request sent
debug1: mux_client_request_session: master session id: 2
debug3: mux_client_read_packet: read header failed: Broken pipe
debug2: Received exit status from master 1
Shared connection to 192.168.1.10 closed.
<192.168.1.10> ESTABLISH SSH CONNECTION FOR USER: None
<192.168.1.10> SSH: EXEC sshpass -d10 ssh -vvv -C -o ControlMaster=auto -o ControlPersist=60s -o ConnectTimeout=60 -o ControlPath=/home/administrator/.ansible/cp/0b3ee26c83 192.168.1.10 '/bin/sh -c '"'"'rm -f -r /home/administrator/.ansible/tmp/ansible-tmp-1567895066.22-102865223087764/ > /dev/null 2>&1 && sleep 0'"'"''
<192.168.1.10> (0, '', 'OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017\r\ndebug1: Reading configuration data /etc/ssh/ssh_config\r\ndebug1: /etc/ssh/ssh_config line 19: Applying options for *\r\ndebug1: auto-mux: Trying existing master\r\ndebug2: fd 3 setting O_NONBLOCK\r\ndebug2: mux_client_hello_exchange: master version 4\r\ndebug3: mux_client_forwards: request forwardings: 0 local, 0 remote\r\ndebug3: mux_client_request_session: entering\r\ndebug3: mux_client_request_alive: entering\r\ndebug3: mux_client_request_alive: done pid = 10512\r\ndebug3: mux_client_request_session: session request sent\r\ndebug1: mux_client_request_session: master session id: 2\r\ndebug3: mux_client_read_packet: read header failed: Broken pipe\r\ndebug2: Received exit status from master 0\r\n')
[WARNING]: 'local: true' specified and user was not found in /etc/passwd. The local user account may already exist if the local account database exists somewhere other than /etc/passwd.
[DEPRECATION WARNING]: Distribution Ubuntu 18.04 on host 192.168.1.10 should use /usr/bin/python3, but is using /usr/bin/python for backward compatibility with prior Ansible releases. A future Ansible
release will default to using the discovered platform python for this host. See https://docs.ansible.com/ansible/2.8/reference_appendices/interpreter_discovery.html for more information. This feature
will be removed in version 2.12. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.
192.168.1.10 | FAILED! => {
"ansible_facts": {
"discovered_interpreter_python": "/usr/bin/python"
},
"changed": false,
"invocation": {
"module_args": {
"append": false,
"authorization": null,
"comment": null,
"create_home": true,
"expires": null,
"force": false,
"generate_ssh_key": null,
"group": "prigroup1",
"groups": null,
"hidden": null,
"home": null,
"local": true,
"login_class": null,
"move_home": false,
"name": "testuser",
"non_unique": false,
"password": null,
"password_lock": null,
"profile": null,
"remove": false,
"role": null,
"seuser": null,
"shell": null,
"skeleton": null,
"ssh_key_bits": 0,
"ssh_key_comment": "ansible-generated on fserver2",
"ssh_key_file": null,
"ssh_key_passphrase": null,
"ssh_key_type": "rsa",
"state": "present",
"system": false,
"uid": null,
"update_password": "always"
}
},
"msg": "Group prigroup1 does not exist"
}
```
| https://github.com/ansible/ansible/issues/61965 | https://github.com/ansible/ansible/pull/77914 | 9f7956ba30abb190875ac1585f6ac9bf10a4712b | 33beeace109a5e918cb21d985e95767ee57ecfe0 | 2019-09-07T22:27:06Z | python | 2022-05-31T17:07:06Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,964 | ["changelogs/fragments/split-host-pattern-empty-strings.yaml", "lib/ansible/inventory/manager.py", "test/integration/targets/inventory_limit/aliases", "test/integration/targets/inventory_limit/hosts.yml", "test/integration/targets/inventory_limit/runme.sh", "test/units/plugins/inventory/test_inventory.py"] | Ansible crashes when `--limit` expression includes superfluous comma | ##### SUMMARY
Running ansible with `--limit a,` or `--limit a,,b` or `--limit ,` leads to (when `-vvv` is added)
```
ERROR! Unexpected Exception, this is probably a bug: string index out of range
the full traceback was:
Traceback (most recent call last):
File ".../ansible/bin/ansible-playbook", line 123, in <module>
exit_code = cli.run()
File ".../ansible/lib/ansible/cli/playbook.py", line 116, in run
CLI.get_host_list(inventory, context.CLIARGS['subset'])
File ".../ansible/lib/ansible/cli/__init__.py", line 487, in get_host_list
inventory.subset(subset)
File ".../ansible/lib/ansible/inventory/manager.py", line 614, in subset
if x[0] == "@":
IndexError: string index out of range
ERROR! Unexpected Exception, this is probably a bug: string index out of range
to see the full traceback, use -vvv
```
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
lib/ansible/inventory/manager.py
##### ANSIBLE VERSION
```
2.9.0
```
Also happens with `devel`, and potentially older ansible versions.
##### STEPS TO REPRODUCE
Run `ansible-playbook playbook.yml --limit a,` for an existing playbook `playbook.yml` (doesn't matter what it actually does, and also does not matter whether you use `a` or a real host name). Same result with `--limit a,,b` or similar expressions where `.split(',')` will lead to an empty string in the resulting list.
##### EXPECTED RESULTS
Ansible complaining about syntax, or simply ignoring the trailing comma / empty parts of the `.split(',')`.
##### ACTUAL RESULTS
```
ERROR! Unexpected Exception, this is probably a bug: string index out of range
to see the full traceback, use -vvv
```
| https://github.com/ansible/ansible/issues/61964 | https://github.com/ansible/ansible/pull/62442 | 8d0c193b251051e459513614e6f7212ecf9f0922 | 987265a6ef920466b44625097ff85f3e845dc8ea | 2019-09-07T19:59:24Z | python | 2019-09-20T20:03:51Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,955 | ["lib/ansible/modules/network/ios/ios_banner.py", "test/units/modules/network/ios/test_ios_banner.py"] | Optional strip on ios_banner | <!--- Verify first that your feature was not already discussed on GitHub -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
<!--- Describe the new feature/improvement briefly below -->
The ios_banner currently strips any text passed to it, making certain banner formats impossible to replicate properly.
##### ISSUE TYPE
- Feature Idea
##### COMPONENT NAME
<!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure -->
ios_banner
##### ADDITIONAL INFORMATION
<!--- Describe how the feature would be used, why it is needed and what it would solve -->
Add a boolean switch to the module params (`strip`, perhaps) that would conditionally strip or not the text passed from the param. Could be optional and default to `True`.
<!--- Paste example playbooks or commands between quotes below -->
```yaml
ios_banner:
strip: no
banner: login
present: yes
text: "{{ lookup('template', 'banner.j2') }}"
```
with the `banner.j2` looking like
```
WARNING
This is a private system if you
do not belong here, bugger off
or something.
```
<!--- HINT: You can also paste gist.github.com links for larger files -->
| https://github.com/ansible/ansible/issues/61955 | https://github.com/ansible/ansible/pull/62573 | da07b98b7a433493728ddb7ac7efbd20b8988776 | 52f3ce8a808f943561803bd664e695fed1841fe8 | 2019-09-06T21:51:14Z | python | 2019-12-27T07:13:09Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,951 | ["changelogs/fragments/ansible-test-execv-wrapper-shebang.yml", "changelogs/fragments/ansible-test-sanity-requirements.yml", "changelogs/fragments/ansible-test-venv-activation.yml", "changelogs/fragments/ansible-test-venv-pythonpath.yml", "test/lib/ansible_test/_internal/delegation.py", "test/lib/ansible_test/_internal/sanity/__init__.py", "test/lib/ansible_test/_internal/util_common.py"] | ansible-test --venv attempts to install to system locations | ##### SUMMARY
After installing ansible-2.90beta1 via pip, ansible-test --venv tries to install to system locations, getting permission denied
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
bin/ansible-test
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
2.9.0beta1
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
N/A
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
* I installed this on CENTOS7 using the python3.6 package
* Installed 2.9.0beta1 from pypi
##### STEPS TO REPRODUCE
```
$ python3.6 -m pip install --user ansible==2.9.0beta1
$ ansible --version
ansible 2.9.0b1
config file = None
configured module search path = ['/home/badger/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /home/badger/.local/lib/python3.6/site-packages/ansible
executable location = /home/badger/.local/bin/ansible
python version = 3.6.8 (default, Apr 25 2019, 21:02:35) [GCC 4.8.5 20150623 (Red Hat 4.8.5-36)]
$ ansible-test sanity --venv --test pep8 lib/ansible/module_utils/basic.py
```
##### EXPECTED RESULTS
ansible-test installs a venv with the required packages for the sanity test and then runs the test on lib/ansible/module_utils/basic.py
##### ACTUAL RESULTS
```
Ignoring coverage: markers "python_version > '3.7'" don't match your environment
Ignoring cryptography: markers "python_version < '2.7'" don't match your environment
Ignoring deepdiff: markers "python_version < '3'" don't match your environment
Ignoring urllib3: markers "python_version < '2.7'" don't match your environment
Ignoring sphinx: markers "python_version < '2.7'" don't match your environment
Ignoring wheel: markers "python_version < '2.7'" don't match your environment
Ignoring yamllint: markers "python_version < '2.7'" don't match your environment
Ignoring paramiko: markers "python_version < '2.7'" don't match your environment
Ignoring pytest: markers "python_version < '2.7'" don't match your environment
Ignoring pytest: markers "python_version == '2.7'" don't match your environment
Ignoring pytest-forked: markers "python_version < '2.7'" don't match your environment
Ignoring requests: markers "python_version < '2.7'" don't match your environment
Ignoring virtualenv: markers "python_version < '2.7'" don't match your environment
Ignoring pyopenssl: markers "python_version < '2.7'" don't match your environment
Ignoring pyyaml: markers "python_version < '2.7'" don't match your environment
Ignoring pycparser: markers "python_version < '2.7'" don't match your environment
Ignoring xmltodict: markers "python_version < '2.7'" don't match your environment
Ignoring lxml: markers "python_version < '2.7'" don't match your environment
Ignoring pyvmomi: markers "python_version < '2.7'" don't match your environment
Collecting voluptuous>=0.11.0 (from -c /home/badger/.local/lib/python3.6/site-packages/ansible_test/_data/requirements/constraints.txt (line 25))
Using cached https://files.pythonhosted.org/packages/24/3b/fe531688c0d9e057fccc0bc9430c0a3d4b90e0d2f015326e659c2944e328/voluptuous-0.11.7.tar.gz
Collecting pylint==2.3.1 (from -c /home/badger/.local/lib/python3.6/site-packages/ansible_test/_data/requirements/constraints.txt (line 45))
Using cached https://files.pythonhosted.org/packages/60/c2/b3f73f4ac008bef6e75bca4992f3963b3f85942e0277237721ef1c151f0d/pylint-2.3.1-py3-none-any.whl
Requirement already satisfied (use --upgrade to upgrade): cryptography in /home/badger/.local/lib/python3.6/site-packages (from -r /home/badger/.local/lib/python3.6/site-packages/ansible_test/_data/requirements/sanity.txt (line 1))
Requirement already satisfied (use --upgrade to upgrade): jinja2 in /home/badger/.local/lib/python3.6/site-packages (from -r /home/badger/.local/lib/python3.6/site-packages/ansible_test/_data/requirements/sanity.txt (line 2))
Collecting pycodestyle (from -r /home/badger/.local/lib/python3.6/site-packages/ansible_test/_data/requirements/sanity.txt (line 3))
Using cached https://files.pythonhosted.org/packages/0e/0c/04a353e104d2f324f8ee5f4b32012618c1c86dd79e52a433b64fceed511b/pycodestyle-2.5.0-py2.py3-none-any.whl
Requirement already satisfied (use --upgrade to upgrade): pyyaml in /home/badger/.local/lib/python3.6/site-packages (from -r /home/badger/.local/lib/python3.6/site-packages/ansible_test/_data/requirements/sanity.txt (line 5))
Requirement already satisfied (use --upgrade to upgrade): rstcheck in /home/badger/.local/lib/python3.6/site-packages (from -r /home/badger/.local/lib/python3.6/site-packages/ansible_test/_data/requirements/sanity.txt (line 6))
Collecting virtualenv (from -r /home/badger/.local/lib/python3.6/site-packages/ansible_test/_data/requirements/sanity.txt (line 7))
Using cached https://files.pythonhosted.org/packages/8b/12/8d4f45b8962b03ac9efefe5ed5053f6b29334d83e438b4fe379d21c0cb8e/virtualenv-16.7.5-py2.py3-none-any.whl
Collecting yamllint (from -r /home/badger/.local/lib/python3.6/site-packages/ansible_test/_data/requirements/sanity.txt (line 9))
Using cached https://files.pythonhosted.org/packages/39/b5/390c956b1aad9a0de18cffa94dba8610b9eca4bd142aa56746e31a388f14/yamllint-1.17.0-py2.py3-none-any.whl
Collecting astroid==2.2.5 (from -c /home/badger/.local/lib/python3.6/site-packages/ansible_test/_data/requirements/constraints.txt (line 41))
Using cached https://files.pythonhosted.org/packages/d5/ad/7221a62a2dbce5c3b8c57fd18e1052c7331adc19b3f27f1561aa6e620db2/astroid-2.2.5-py3-none-any.whl
Collecting mccabe==0.6.1 (from -c /home/badger/.local/lib/python3.6/site-packages/ansible_test/_data/requirements/constraints.txt (line 44))
Using cached https://files.pythonhosted.org/packages/87/89/479dc97e18549e21354893e4ee4ef36db1d237534982482c3681ee6e7b57/mccabe-0.6.1-py2.py3-none-any.whl
Collecting isort==4.3.15 (from -c /home/badger/.local/lib/python3.6/site-packages/ansible_test/_data/requirements/constraints.txt (line 42))
Using cached https://files.pythonhosted.org/packages/b6/89/3137d13dd30a0d063435661950f6dfd50957532989e49aef652f490ef616/isort-4.3.15-py2.py3-none-any.whl
Requirement already satisfied (use --upgrade to upgrade): asn1crypto>=0.21.0 in /home/badger/.local/lib/python3.6/site-packages (from cryptography->-r /home/badger/.local/lib/python3.6/site-packages/ansible_test/_data/requirements/sanity.txt (line 1))
Requirement already satisfied (use --upgrade to upgrade): six>=1.4.1 in /home/badger/.local/lib/python3.6/site-packages (from cryptography->-r /home/badger/.local/lib/python3.6/site-packages/ansible_test/_data/requirements/sanity.txt (line 1))
Requirement already satisfied (use --upgrade to upgrade): cffi!=1.11.3,>=1.8 in /home/badger/.local/lib/python3.6/site-packages (from cryptography->-r /home/badger/.local/lib/python3.6/site-packages/ansible_test/_data/requirements/sanity.txt (line 1))
Requirement already satisfied (use --upgrade to upgrade): MarkupSafe>=0.23 in /home/badger/.local/lib/python3.6/site-packages (from jinja2->-r /home/badger/.local/lib/python3.6/site-packages/ansible_test/_data/requirements/sanity.txt (line 2))
Requirement already satisfied (use --upgrade to upgrade): docutils>=0.7 in /home/badger/.local/lib/python3.6/site-packages (from rstcheck->-r /home/badger/.local/lib/python3.6/site-packages/ansible_test/_data/requirements/sanity.txt (line 6))
Collecting pathspec>=0.5.3 (from yamllint->-r /home/badger/.local/lib/python3.6/site-packages/ansible_test/_data/requirements/sanity.txt (line 9))
Using cached https://files.pythonhosted.org/packages/84/2a/bfee636b1e2f7d6e30dd74f49201ccfa5c3cf322d44929ecc6c137c486c5/pathspec-0.5.9.tar.gz
Collecting typed-ast==1.4.0 (from -c /home/badger/.local/lib/python3.6/site-packages/ansible_test/_data/requirements/constraints.txt (line 46))
Using cached https://files.pythonhosted.org/packages/31/d3/9d1802c161626d0278bafb1ffb32f76b9d01e123881bbf9d91e8ccf28e18/typed_ast-1.4.0-cp36-cp36m-manylinux1_x86_64.whl
Collecting wrapt==1.11.1 (from -c /home/badger/.local/lib/python3.6/site-packages/ansible_test/_data/requirements/constraints.txt (line 47))
Using cached https://files.pythonhosted.org/packages/67/b2/0f71ca90b0ade7fad27e3d20327c996c6252a2ffe88f50a95bba7434eda9/wrapt-1.11.1.tar.gz
Collecting lazy-object-proxy==1.3.1 (from -c /home/badger/.local/lib/python3.6/site-packages/ansible_test/_data/requirements/constraints.txt (line 43))
Using cached https://files.pythonhosted.org/packages/65/1f/2043ec33066e779905ed7e6580384425fdc7dc2ac64d6931060c75b0c5a3/lazy_object_proxy-1.3.1-cp36-cp36m-manylinux1_x86_64.whl
Requirement already satisfied (use --upgrade to upgrade): pycparser in /home/badger/.local/lib/python3.6/site-packages (from cffi!=1.11.3,>=1.8->cryptography->-r /home/badger/.local/lib/python3.6/site-packages/ansible_test/_data/requirements/sanity.txt (line 1))
Installing collected packages: voluptuous, typed-ast, wrapt, lazy-object-proxy, astroid, isort, mccabe, pylint, pycodestyle, virtualenv, pathspec, yamllint
Running setup.py install for voluptuous ... error
Complete output from command /var/tmp/tmpi3kn3062/python3.6 -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-n_ufdj0i/voluptuous/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-nzpu8u3y-record/install-record.txt --single-version-externally-managed --compile:
running install
running build
running build_py
creating build
creating build/lib
creating build/lib/voluptuous
copying voluptuous/__init__.py -> build/lib/voluptuous
copying voluptuous/error.py -> build/lib/voluptuous
copying voluptuous/humanize.py -> build/lib/voluptuous
copying voluptuous/schema_builder.py -> build/lib/voluptuous
copying voluptuous/util.py -> build/lib/voluptuous
copying voluptuous/validators.py -> build/lib/voluptuous
running install_lib
creating /usr/local/lib/python3.6
error: could not create '/usr/local/lib/python3.6': Permission denied
----------------------------------------
Command "/var/tmp/tmpi3kn3062/python3.6 -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-n_ufdj0i/voluptuous/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-nzpu8u3y-record/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /tmp/pip-build-n_ufdj0i/voluptuous/
ERROR: Command "/var/tmp/tmpi3kn3062/python3.6 -m pip.__main__ install --disable-pip-version-check -c /home/badger/.local/lib/python3.6/site-packages/ansible_test/_data/requirements/constraints.txt -r /home/badger/.local/lib/python3.6/site-packages/ansible_test/_data/requirements/sanity.txt" returned exit status 1.
ERROR: Command "/usr/bin/env ANSIBLE_TEST_CONTENT_ROOT=/home/badger/ansible LC_ALL=en_US.UTF-8 /var/tmp/tmpi3kn3062/python3.6 /home/badger/.local/bin/ansible-test sanity --test pep8 lib/ansible/module_utils/basic.py --metadata metadata-c4as9ur5.json --truncate 117 --color yes --requirements" returned exit status 1.
```
| https://github.com/ansible/ansible/issues/61951 | https://github.com/ansible/ansible/pull/62033 | e3ea89801bae73921b298e7b4628860a272e942c | c77ab110514900ee439c7281a1d1dd14504cf44a | 2019-09-06T18:15:00Z | python | 2019-09-10T01:32:29Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,946 | ["changelogs/fragments/ansible-test-execv-wrapper-shebang.yml", "changelogs/fragments/ansible-test-sanity-requirements.yml", "changelogs/fragments/ansible-test-venv-activation.yml", "changelogs/fragments/ansible-test-venv-pythonpath.yml", "test/lib/ansible_test/_internal/delegation.py", "test/lib/ansible_test/_internal/sanity/__init__.py", "test/lib/ansible_test/_internal/util_common.py"] | ansible-test --venv fails to find its library | ##### SUMMARY
When installed from the ansible-2.9 PPA https://launchpad.net/~ansible/+archive/ubuntu/ansible-2.9 or from the nightly ansible rpms for RHEL7, ansible-test --venv fails to find its internal libraries
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
<!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure -->
bin/ansible-test
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
2.9.0beta1 devel
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
N/A
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
Ubuntu18 or CentOS7. I suspect that this is irrespective of the OS but may be related to how we are presently packaging. Ubuntu18 PPA and CentOS7 are both using python-2.7 with the separate python-virtualenv package at this time.
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
<!--- Paste example playbooks or commands between quotes below -->
I did these steps in a fresh centos7 VM:
Create a yum repo file for the nightlies:
```
$ cat ansible-nightly.repo (08:59:07)
[ansible-nightly]
name=Nightly Ansible packaging - $basearch
baseurl=https://releases.ansible.com/ansible/rpm/nightly/devel/epel-7-$basearch/
failovermethod=priority
enabled=0
#gpgcheck=1
#gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7
```
use the ansible-nightly repo to install ansible-test
```
sudo yum install ansible-test --enablerepo=ansible-nightly --nogpgcheck
# ansible-test package and ansible package will be installed
$ ansible --version
ansible 2.10.0.dev0
config file = /etc/ansible/ansible.cfg
configured module search path = [u'/home/badger/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python2.7/site-packages/ansible
executable location = /usr/bin/ansible
python version = 2.7.5 (default, Jun 20 2019, 20:27:34) [GCC 4.8.5 20150623 (Red Hat 4.8.5-36)]
$ git clone git://github.com/ansible/ansible
$ cd ansible
$ ansible-test sanity --venv --test pep8 lib/ansible/module_utils/basic.py
Traceback (most recent call last):
File "/usr/bin/ansible-test", line 28, in <module>
main()
File "/usr/bin/ansible-test", line 22, in main
from ansible_test._internal.cli import main as cli_main
ImportError: No module named ansible_test._internal.cli
ERROR: Command "/usr/bin/env ANSIBLE_TEST_CONTENT_ROOT=/home/badger/ansible LC_ALL=en_US.UTF-8 /var/tmp/tmpYdP0oT/python2.7 /usr/bin/ansible-test sanity --test pep8 lib/ansible/module_utils/basic.py --metadata metadata-X1O5jT.json --truncate 117 --color yes --requirements" returned exit status 1.
```
<!--- HINT: You can paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
ansible-test works with the --venv switch
##### ACTUAL RESULTS
I believe this is the venv directory: ```~/ansible/test/results/.tmp/delegation/python2.7```
Contents of site-packages there:
```
[pts/0@centos7-master ~/ansible/test/results/.tmp/delegation/python2.7]$ ls -l lib/python2.7/site-packages
total 20
-rw-rw-r--. 1 badger badger 126 Sep 5 14:39 easy_install.py
-rw-rw-r--. 1 badger badger 315 Sep 5 14:39 easy_install.pyc
drwxrwxr-x. 10 badger badger 4096 Sep 5 14:39 pip
drwxrwxr-x. 2 badger badger 155 Sep 5 14:39 pip-9.0.1.dist-info
drwxrwxr-x. 4 badger badger 74 Sep 5 14:39 pkg_resources
drwxrwxr-x. 4 badger badger 4096 Sep 5 14:39 setuptools
drwxrwxr-x. 2 badger badger 199 Sep 5 14:39 setuptools-28.8.0.dist-info
drwxrwxr-x. 5 badger badger 4096 Sep 5 14:39 wheel
drwxrwxr-x. 2 badger badger 174 Sep 5 14:39 wheel-0.29.0.dist-info
```
Possible cause: ansible and/or ansible_test needs to be installed into the venv before ansible-test is re-invoked? | https://github.com/ansible/ansible/issues/61946 | https://github.com/ansible/ansible/pull/62033 | e3ea89801bae73921b298e7b4628860a272e942c | c77ab110514900ee439c7281a1d1dd14504cf44a | 2019-09-06T16:53:27Z | python | 2019-09-10T01:32:29Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,938 | ["test/integration/targets/mongodb_replicaset/tasks/main.yml", "test/integration/targets/mongodb_replicaset/tasks/mongod_replicaset.yml"] | mongod_replicaset: test fails with Wait for mongod to start responding port={{ item }} | ##### SUMMARY
Time to time, mongodb fails to start and the functional test fails because of that.
e.g:
- https://app.shippable.com/github/ansible/ansible/runs/142156/73/tests
- https://app.shippable.com/github/ansible/ansible/runs/143055/73/tests
- https://app.shippable.com/github/ansible/ansible/runs/143055/67/tests
```
mongodb_replicaset-v2r_u7pa / /root/.ansible/test/tmp/mongodb_replicaset-nirs74ib-ÅÑŚÌβŁÈ/test/integration/targets/mongodb_replicaset/tasks/mongod_replicaset.yml:41 / [testhost] testhost: mongodb_replicaset : Wait for mongod to start responding port={{ item }}
failure: All items completed
```
```yaml
{
"changed": false,
"msg": "All items completed",
"results": [
{
"ansible_loop_var": "item",
"changed": false,
"elapsed": 300,
"failed": true,
"invocation": {
"module_args": {
"active_connection_states": [
"ESTABLISHED",
"FIN_WAIT1",
"FIN_WAIT2",
"SYN_RECV",
"SYN_SENT",
"TIME_WAIT"
],
"connect_timeout": 5,
"delay": 0,
"exclude_hosts": null,
"host": "127.0.0.1",
"msg": null,
"path": null,
"port": 3001,
"search_regex": null,
"sleep": 1,
"state": "started",
"timeout": 300
}
},
"item": 3001,
"msg": "Timeout when waiting for 127.0.0.1:3001"
},
{
"ansible_loop_var": "item",
"changed": false,
"elapsed": 0,
"failed": false,
"invocation": {
"module_args": {
"active_connection_states": [
"ESTABLISHED",
"FIN_WAIT1",
"FIN_WAIT2",
"SYN_RECV",
"SYN_SENT",
"TIME_WAIT"
],
"connect_timeout": 5,
"delay": 0,
"exclude_hosts": null,
"host": "127.0.0.1",
"msg": null,
"path": null,
"port": 3002,
"search_regex": null,
"sleep": 1,
"state": "started",
"timeout": 300
}
},
"item": 3002,
"match_groupdict": {},
"match_groups": [],
"path": null,
"port": 3002,
"search_regex": null,
"state": "started"
},
{
"ansible_loop_var": "item",
"changed": false,
"elapsed": 0,
"failed": false,
"invocation": {
"module_args": {
"active_connection_states": [
"ESTABLISHED",
"FIN_WAIT1",
"FIN_WAIT2",
"SYN_RECV",
"SYN_SENT",
"TIME_WAIT"
],
"connect_timeout": 5,
"delay": 0,
"exclude_hosts": null,
"host": "127.0.0.1",
"msg": null,
"path": null,
"port": 3003,
"search_regex": null,
"sleep": 1,
"state": "started",
"timeout": 300
}
},
"item": 3003,
"match_groupdict": {},
"match_groups": [],
"path": null,
"port": 3003,
"search_regex": null,
"state": "started"
}
]
}
```
<!--- Explain the problem briefly below -->
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
<!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure -->
mongod_replicaset
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
devel
``` | https://github.com/ansible/ansible/issues/61938 | https://github.com/ansible/ansible/pull/62627 | 85eba9d86084f083b70a808e2c5a4fc28427ab17 | cee55ab7187df23ffa3c577ab1cbe15334cb38fa | 2019-09-06T15:40:59Z | python | 2019-09-19T21:19:48Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,921 | ["changelogs/fragments/61921-gitlab_user.yml", "docs/docsite/rst/porting_guides/porting_guide_2.10.rst", "lib/ansible/modules/source_control/gitlab/gitlab_user.py"] | gitlab_user requires email, name, and password arguments when deleting a user | ##### SUMMARY
In th `gitlab_user` module the `email`, `name`, and `password` arguments are required.
That is perfectly fine when creating a new user as this information is needed.
However, these three arguments are also required when deleting a user (state==absent), even though they are not used by the module for this action.
The module fails with an error if these arguments are not passed in. You are forced to pass in blank (or dummy) values.
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
gitlab_user
##### ANSIBLE VERSION
```paste below
ansible 2.8.4
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
Manjaro Linux 18.0.4
##### STEPS TO REPRODUCE
```yaml
- name: Delete user account
gitlab_user:
server_url: "{{ gitlab_url }}"
api_token: "{{ token }}"
username: "{{ username }}"
state: absent
```
##### EXPECTED RESULTS
GitLab user should be successfully deleted. Only the `username` is required to find and delete the user.
##### ACTUAL RESULTS
```
fatal: [localhost]: FAILED! => {"changed": false, "msg": "missing required arguments: name, password, email"}
```
##### WORKAROUND
```yaml
- name: Delete user account
gitlab_user:
server_url: "{{ gitlab_url }}"
api_token: "{{ token }}"
username: "{{ username }}"
email: ""
name: ""
password: ""
state: absent
``` | https://github.com/ansible/ansible/issues/61921 | https://github.com/ansible/ansible/pull/64832 | 9ee601288c45a5ca2c1bc37196b9aade2966ca0d | eac7fa186088bbcb82c1914b124cfb93d9436202 | 2019-09-06T08:39:20Z | python | 2019-11-14T11:51:14Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,898 | ["lib/ansible/modules/source_control/gitlab_deploy_key.py", "lib/ansible/modules/source_control/gitlab_group.py", "lib/ansible/modules/source_control/gitlab_hook.py", "lib/ansible/modules/source_control/gitlab_project.py", "lib/ansible/modules/source_control/gitlab_runner.py", "lib/ansible/modules/source_control/gitlab_user.py"] | gitlab_user contains deprecated call to be removed in 2.10 | ##### SUMMARY
gitlab_user contains call to Display.deprecated or AnsibleModule.deprecate and is scheduled for removal
```
lib/ansible/modules/source_control/gitlab_user.py:414:4: ansible-deprecated-version: Deprecated version ('2.10') found in call to Display.deprecated or AnsibleModule.deprecate
```
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
```
lib/ansible/modules/source_control/gitlab_user.py
```
##### ANSIBLE VERSION
```
2.10
```
##### CONFIGURATION
N/A
##### OS / ENVIRONMENT
N/A
##### STEPS TO REPRODUCE
N/A
##### EXPECTED RESULTS
N/A
##### ACTUAL RESULTS
N/A
| https://github.com/ansible/ansible/issues/61898 | https://github.com/ansible/ansible/pull/61912 | 331d51fb16b05f09d3d24d6d6f8d705fa0db4ba7 | f92c99b4135327629cc2c92995f00102fcf2f681 | 2019-09-05T20:41:20Z | python | 2019-10-20T11:38:08Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,897 | ["lib/ansible/modules/source_control/gitlab_deploy_key.py", "lib/ansible/modules/source_control/gitlab_group.py", "lib/ansible/modules/source_control/gitlab_hook.py", "lib/ansible/modules/source_control/gitlab_project.py", "lib/ansible/modules/source_control/gitlab_runner.py", "lib/ansible/modules/source_control/gitlab_user.py"] | gitlab_runner contains deprecated call to be removed in 2.10 | ##### SUMMARY
gitlab_runner contains call to Display.deprecated or AnsibleModule.deprecate and is scheduled for removal
```
lib/ansible/modules/source_control/gitlab_runner.py:291:4: ansible-deprecated-version: Deprecated version ('2.10') found in call to Display.deprecated or AnsibleModule.deprecate
```
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
```
lib/ansible/modules/source_control/gitlab_runner.py
```
##### ANSIBLE VERSION
```
2.10
```
##### CONFIGURATION
N/A
##### OS / ENVIRONMENT
N/A
##### STEPS TO REPRODUCE
N/A
##### EXPECTED RESULTS
N/A
##### ACTUAL RESULTS
N/A
| https://github.com/ansible/ansible/issues/61897 | https://github.com/ansible/ansible/pull/61912 | 331d51fb16b05f09d3d24d6d6f8d705fa0db4ba7 | f92c99b4135327629cc2c92995f00102fcf2f681 | 2019-09-05T20:41:19Z | python | 2019-10-20T11:38:08Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,896 | ["lib/ansible/modules/source_control/gitlab_deploy_key.py", "lib/ansible/modules/source_control/gitlab_group.py", "lib/ansible/modules/source_control/gitlab_hook.py", "lib/ansible/modules/source_control/gitlab_project.py", "lib/ansible/modules/source_control/gitlab_runner.py", "lib/ansible/modules/source_control/gitlab_user.py"] | gitlab_project contains deprecated call to be removed in 2.10 | ##### SUMMARY
gitlab_project contains call to Display.deprecated or AnsibleModule.deprecate and is scheduled for removal
```
lib/ansible/modules/source_control/gitlab_project.py:292:4: ansible-deprecated-version: Deprecated version ('2.10') found in call to Display.deprecated or AnsibleModule.deprecate
```
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
```
lib/ansible/modules/source_control/gitlab_project.py
```
##### ANSIBLE VERSION
```
2.10
```
##### CONFIGURATION
N/A
##### OS / ENVIRONMENT
N/A
##### STEPS TO REPRODUCE
N/A
##### EXPECTED RESULTS
N/A
##### ACTUAL RESULTS
N/A
| https://github.com/ansible/ansible/issues/61896 | https://github.com/ansible/ansible/pull/61912 | 331d51fb16b05f09d3d24d6d6f8d705fa0db4ba7 | f92c99b4135327629cc2c92995f00102fcf2f681 | 2019-09-05T20:41:18Z | python | 2019-10-20T11:38:08Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,895 | ["lib/ansible/modules/source_control/gitlab_deploy_key.py", "lib/ansible/modules/source_control/gitlab_group.py", "lib/ansible/modules/source_control/gitlab_hook.py", "lib/ansible/modules/source_control/gitlab_project.py", "lib/ansible/modules/source_control/gitlab_runner.py", "lib/ansible/modules/source_control/gitlab_user.py"] | gitlab_hook contains deprecated call to be removed in 2.10 | ##### SUMMARY
gitlab_hook contains call to Display.deprecated or AnsibleModule.deprecate and is scheduled for removal
```
lib/ansible/modules/source_control/gitlab_hook.py:302:4: ansible-deprecated-version: Deprecated version ('2.10') found in call to Display.deprecated or AnsibleModule.deprecate
```
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
```
lib/ansible/modules/source_control/gitlab_hook.py
```
##### ANSIBLE VERSION
```
2.10
```
##### CONFIGURATION
N/A
##### OS / ENVIRONMENT
N/A
##### STEPS TO REPRODUCE
N/A
##### EXPECTED RESULTS
N/A
##### ACTUAL RESULTS
N/A
| https://github.com/ansible/ansible/issues/61895 | https://github.com/ansible/ansible/pull/61912 | 331d51fb16b05f09d3d24d6d6f8d705fa0db4ba7 | f92c99b4135327629cc2c92995f00102fcf2f681 | 2019-09-05T20:41:17Z | python | 2019-10-20T11:38:08Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,894 | ["lib/ansible/modules/source_control/gitlab_deploy_key.py", "lib/ansible/modules/source_control/gitlab_group.py", "lib/ansible/modules/source_control/gitlab_hook.py", "lib/ansible/modules/source_control/gitlab_project.py", "lib/ansible/modules/source_control/gitlab_runner.py", "lib/ansible/modules/source_control/gitlab_user.py"] | gitlab_group contains deprecated call to be removed in 2.10 | ##### SUMMARY
gitlab_group contains call to Display.deprecated or AnsibleModule.deprecate and is scheduled for removal
```
lib/ansible/modules/source_control/gitlab_group.py:273:4: ansible-deprecated-version: Deprecated version ('2.10') found in call to Display.deprecated or AnsibleModule.deprecate
```
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
```
lib/ansible/modules/source_control/gitlab_group.py
```
##### ANSIBLE VERSION
```
2.10
```
##### CONFIGURATION
N/A
##### OS / ENVIRONMENT
N/A
##### STEPS TO REPRODUCE
N/A
##### EXPECTED RESULTS
N/A
##### ACTUAL RESULTS
N/A
| https://github.com/ansible/ansible/issues/61894 | https://github.com/ansible/ansible/pull/61912 | 331d51fb16b05f09d3d24d6d6f8d705fa0db4ba7 | f92c99b4135327629cc2c92995f00102fcf2f681 | 2019-09-05T20:41:16Z | python | 2019-10-20T11:38:08Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,893 | ["lib/ansible/modules/source_control/gitlab_deploy_key.py", "lib/ansible/modules/source_control/gitlab_group.py", "lib/ansible/modules/source_control/gitlab_hook.py", "lib/ansible/modules/source_control/gitlab_project.py", "lib/ansible/modules/source_control/gitlab_runner.py", "lib/ansible/modules/source_control/gitlab_user.py"] | gitlab_deploy_key contains deprecated call to be removed in 2.10 | ##### SUMMARY
gitlab_deploy_key contains call to Display.deprecated or AnsibleModule.deprecate and is scheduled for removal
```
lib/ansible/modules/source_control/gitlab_deploy_key.py:244:4: ansible-deprecated-version: Deprecated version ('2.10') found in call to Display.deprecated or AnsibleModule.deprecate
```
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
```
lib/ansible/modules/source_control/gitlab_deploy_key.py
```
##### ANSIBLE VERSION
```
2.10
```
##### CONFIGURATION
N/A
##### OS / ENVIRONMENT
N/A
##### STEPS TO REPRODUCE
N/A
##### EXPECTED RESULTS
N/A
##### ACTUAL RESULTS
N/A
| https://github.com/ansible/ansible/issues/61893 | https://github.com/ansible/ansible/pull/61912 | 331d51fb16b05f09d3d24d6d6f8d705fa0db4ba7 | f92c99b4135327629cc2c92995f00102fcf2f681 | 2019-09-05T20:41:15Z | python | 2019-10-20T11:38:08Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,892 | ["changelogs/fragments/61961-pacman_remove_recurse_option.yaml", "docs/docsite/rst/porting_guides/porting_guide_2.10.rst", "lib/ansible/modules/packaging/os/pacman.py"] | pacman contains deprecated call to be removed in 2.10 | ##### SUMMARY
pacman contains call to Display.deprecated or AnsibleModule.deprecate and is scheduled for removal
```
lib/ansible/modules/packaging/os/pacman.py:456:8: ansible-deprecated-version: Deprecated version ('2.10') found in call to Display.deprecated or AnsibleModule.deprecate
```
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
```
lib/ansible/modules/packaging/os/pacman.py
```
##### ANSIBLE VERSION
```
2.10
```
##### CONFIGURATION
N/A
##### OS / ENVIRONMENT
N/A
##### STEPS TO REPRODUCE
N/A
##### EXPECTED RESULTS
N/A
##### ACTUAL RESULTS
N/A
| https://github.com/ansible/ansible/issues/61892 | https://github.com/ansible/ansible/pull/61961 | e55f46f3026f4bc17f5c51341bb568b0886e4dfe | 25ac7042b070b22c5377f7a43399c19060a38966 | 2019-09-05T20:41:14Z | python | 2019-10-02T22:02:06Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,891 | ["changelogs/fragments/61891-get_url-remove-deprecated-string-headers.yml", "lib/ansible/modules/net_tools/basics/get_url.py", "test/integration/targets/get_url/tasks/main.yml"] | get_url contains deprecated call to be removed in 2.10 | ##### SUMMARY
get_url contains call to Display.deprecated or AnsibleModule.deprecate and is scheduled for removal
```
lib/ansible/modules/net_tools/basics/get_url.py:478:12: ansible-deprecated-version: Deprecated version ('2.10') found in call to Display.deprecated or AnsibleModule.deprecate
```
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
```
lib/ansible/modules/net_tools/basics/get_url.py
```
##### ANSIBLE VERSION
```
2.10
```
##### CONFIGURATION
N/A
##### OS / ENVIRONMENT
N/A
##### STEPS TO REPRODUCE
N/A
##### EXPECTED RESULTS
N/A
##### ACTUAL RESULTS
N/A
| https://github.com/ansible/ansible/issues/61891 | https://github.com/ansible/ansible/pull/66649 | abc8b0ae73af6c7d303c0bd25cc9ad6b5bba1d3a | 365f2aaed1e628414898ec7106da272c245c52a2 | 2019-09-05T20:41:12Z | python | 2020-01-28T15:39:40Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,890 | ["docs/docsite/rst/porting_guides/porting_guide_2.10.rst", "lib/ansible/modules/crypto/acme/_letsencrypt.py", "lib/ansible/modules/crypto/acme/_letsencrypt.py", "lib/ansible/modules/crypto/acme/acme_certificate.py"] | acme_certificate contains deprecated call to be removed in 2.10 | ##### SUMMARY
acme_certificate contains call to Display.deprecated or AnsibleModule.deprecate and is scheduled for removal
```
lib/ansible/modules/crypto/acme/acme_certificate.py:1024:8: ansible-deprecated-version: Deprecated version ('2.10') found in call to Display.deprecated or AnsibleModule.deprecate
```
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
```
lib/ansible/modules/crypto/acme/acme_certificate.py
```
##### ANSIBLE VERSION
```
2.10
```
##### CONFIGURATION
N/A
##### OS / ENVIRONMENT
N/A
##### STEPS TO REPRODUCE
N/A
##### EXPECTED RESULTS
N/A
##### ACTUAL RESULTS
N/A
| https://github.com/ansible/ansible/issues/61890 | https://github.com/ansible/ansible/pull/61648 | 14bccef2c207584bf19132fbbf10ab2237746b9e | a0bec0bc327d29f446a031abc803b8d2cad1949f | 2019-09-05T20:41:11Z | python | 2019-09-14T21:24:32Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,889 | ["changelogs/fragments/61889-change-transform_invalid_group_chars-default.yml", "lib/ansible/inventory/group.py"] | group contains deprecated call to be removed in 2.10 | ##### SUMMARY
group contains call to Display.deprecated or AnsibleModule.deprecate and is scheduled for removal
```
b/ansible/inventory/group.py:54:20: ansible-deprecated-version: Deprecated version ('2.10') found in call to Display.deprecated or AnsibleModule.deprecate
```
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
```
b/ansible/inventory/group.py
```
##### ANSIBLE VERSION
```
2.10
```
##### CONFIGURATION
N/A
##### OS / ENVIRONMENT
N/A
##### STEPS TO REPRODUCE
N/A
##### EXPECTED RESULTS
N/A
##### ACTUAL RESULTS
N/A
| https://github.com/ansible/ansible/issues/61889 | https://github.com/ansible/ansible/pull/66650 | cdaf7da11a2cdffe7c9bd5cff7d1b2acfa8e95e1 | 6086ea62ee5e47f3071410b302a10392d6e2437a | 2019-09-05T20:41:10Z | python | 2020-05-13T14:16:32Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,884 | ["test/lib/ansible_test/_data/sanity/import/importer.py", "test/lib/ansible_test/_internal/sanity/import.py"] | Import test doesn't recognize relative imports in a module inside collection | <!--- Verify first that your issue is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
<!--- Explain the problem briefly below -->
When trying to check support of relative imports in modules inside collections, import sanity test fails giving below error
```
Running sanity test 'import' with Python 2.7
ERROR: Found 1 import issue(s) on python 2.7 which need to be resolved:
ERROR: plugins/modules/rubrik_managed_volume.py:8:0: ValueError: Attempted relative import in non-package
WARNING: Skipping sanity test 'import' on Python 3.5 due to missing interpreter.
WARNING: Skipping sanity test 'import' on Python 3.6 due to missing interpreter.
Running sanity test 'import' with Python 3.7
ERROR: Found 1 import issue(s) on python 3.7 which need to be resolved:
ERROR: plugins/modules/rubrik_managed_volume.py:8:0: ImportError: attempted relative import with no known parent package
```
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
<!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure -->
ansible-test sanity import
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
ansible 2.9.0b1
config file = /home/abehl/.ansible/collections/ansible_collections/rubrikinc/rubrik/ansible.cfg
configured module search path = ['/home/abehl/.ansible/collections/ansible_collections/rubrikinc/rubrik/library']
ansible python module location = /home/abehl/work/src/anshul_ansible/ansible/lib/ansible
executable location = /home/abehl/work/src/anshul_ansible/ansible/bin/ansible
python version = 3.7.3 (default, May 11 2019, 00:38:04) [GCC 9.1.1 20190503 (Red Hat 9.1.1-1)]
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
Create a collection with modules having relative imports
Try running ansible-test sanity on the same module
<!--- Paste example playbooks or commands between quotes below -->
```yaml
```
<!--- HINT: You can paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
Relative imports should pass
##### ACTUAL RESULTS
<!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) -->
ansible import tests doesn't recognize relative import
<!--- Paste verbatim command output between quotes -->
```paste below
```
| https://github.com/ansible/ansible/issues/61884 | https://github.com/ansible/ansible/pull/63830 | b52d7155678017340fd39711b335ec2c582d6783 | 92ccdeac31902803c953792d9af929c7edf93f60 | 2019-09-05T19:06:11Z | python | 2019-10-23T06:00:35Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,876 | ["lib/ansible/plugins/connection/network_cli.py"] | Nxos privilage escalation not working properly | ##### SUMMARY
I found another issue that is similar to the issue reported in https://github.com/ansible/ansible/issues/61568.
In this case if I run the playbook described below I encounter the following issue:
```
TASK [nxos_become : run commands with become] ***********************************************************************************************************************************************************
task path: /root/agents-ci/ansible/test/integration/targets/nxos_become/tests/cli/sanity.yaml:7
<n3k.example.com> attempting to start connection
<n3k.example.com> using connection plugin network_cli
<n3k.example.com> found existing local domain socket, using it!
<n3k.example.com> updating play_context for connection
<n3k.example.com>
The full traceback is:
Traceback (most recent call last):
File "/root/agents-ci/ansible/bin/ansible-connection", line 300, in main
conn.update_play_context(pc_data)
File "/root/agents-ci/ansible/lib/ansible/module_utils/connection.py", line 185, in __rpc__
raise ConnectionError(to_text(msg, errors='surrogate_then_replace'), code=code)
ConnectionError: 'NoneType' object has no attribute 'endswith'
fatal: [n3k-priv]: FAILED! => {
"msg": "'NoneType' object has no attribute 'endswith'"
}
```
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
nxos
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
ansible 2.10.0.dev0
config file = /root/agents-ci/ansible/test/integration/ansible.cfg
configured module search path = [u'/root/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /root/agents-ci/ansible/lib/ansible
executable location = /root/agents-ci/ansible/bin/ansible
python version = 2.7.12 (default, Dec 4 2017, 14:50:18) [GCC 5.4.0 20160609]
```
##### STEPS TO REPRODUCE
Just like I describe in https://github.com/ansible/ansible/issues/61568, if I checkout the commit right before https://github.com/ansible/ansible/commit/7d3c4a88823846cbcea7c61de38658a6d63d4265 I don't see the problem.
I decided to open a separate issue for this though because if I patch in the potential fix (https://github.com/ansible/ansible/pull/61570) I still see the issue.
##### EXPECTED RESULTS
Test should pass on all NXOS platforms.
##### ACTUAL RESULTS
Test fails with error message
```
Traceback (most recent call last):
File "/root/agents-ci/ansible/bin/ansible-connection", line 300, in main
conn.update_play_context(pc_data)
File "/root/agents-ci/ansible/lib/ansible/module_utils/connection.py", line 185, in __rpc__
raise ConnectionError(to_text(msg, errors='surrogate_then_replace'), code=code)
ConnectionError: 'NoneType' object has no attribute 'endswith'
```
Here is the playbook that exposes the issue.
Command to execute the playbook: `ansible-playbook -i ~/hosts nxos.yaml -vvvv`
**nxos.yaml**
```yaml
---
# This first play configures a new user called test_ansible and sets
# the enable secret
- name: Setup test user for role validation
hosts: nxos
gather_facts: no
connection: network_cli
tasks:
- set_fact: nxos_priv_host="{{ hostvars[inventory_hostname]["groups"]["nxos_privilage_user"][0] }}"
- set_fact: priv_password="{{ hostvars[nxos_priv_host]["ansible_ssh_pass"] }}"
- name: Enable Feature Privilege
nxos_config:
lines:
- feature privilege
- name: Configure user ansible_test with role priv-14
nxos_config:
lines:
- no username test_ansible
- "username test_ansible password {{ priv_password }} role priv-14"
- enable secret 0 cisco
# This second play uses the nxos_become role to verify that ansible
# can login as the test user created in the first play and then use
# become to enable a higher privilage level
- name: Verify privliage role escalation using become
hosts: nxos_privilage_user
gather_facts: no
connection: local
vars:
debug: false
roles:
- { role: nxos_become }
# This third and final play is used to cleanup the test user
- name: Cleanup test user
hosts: nxos
gather_facts: no
connection: network_cli
tasks:
- name: Remove user ansible_test
nxos_config:
lines:
- no username test_ansible
- no enable secret
```
**nxos_become role**
Everything committed into the current `devel` role but replace `targets/nxos_become/tests/cli/sanity.yaml` with:
```yaml
---
- debug: msg="START connection={{ ansible_connection }}/sanity.yaml"
- debug: msg="Using provider={{ connection.transport }}/sanity.yaml"
when: ansible_connection == "local"
- block:
- name: run commands with become
nxos_command:
commands: 'show privilege'
become: yes
register: result
- assert:
that:
- "'Current privilege level: 15' in result['stdout'][0]"
- debug: msg="END connection={{ ansible_connection }}/sanity.yaml"
``` | https://github.com/ansible/ansible/issues/61876 | https://github.com/ansible/ansible/pull/61797 | 394a05108dc79efc8d917fa0febbfcf721e94b61 | a365e77cc350ff5ce2dfaf421d7a3f54152cf187 | 2019-09-05T18:09:22Z | python | 2019-09-05T18:48:16Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,869 | ["lib/ansible/plugins/httpapi/eos.py"] | eos_system : configure domain_list using platform agnostic module random failure | <!--- Verify first that your issue is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
<!--- Explain the problem briefly below -->
This is to help track a random failure we are seeing in eos testing.
https://object-storage-ca-ymq-1.vexxhost.net/v1/a0b4156a37f9453eb4ec7db5422272df/ansible_79/61779/2a3bc59e39230ad945d42da08a8aad3f91dee027/third-party-check/ansible-test-network-integration-eos-python37/31d1710/controller/ara-report/result/493a2986-7709-41bc-bbe7-5df954edb93a/
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
<!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure -->
eos_system
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
zuul.ansible.com
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
<!--- Paste example playbooks or commands between quotes below -->
```yaml
```
<!--- HINT: You can paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
##### ACTUAL RESULTS
<!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) -->
<!--- Paste verbatim command output between quotes -->
```paste below
Traceback (most recent call last):
File "/home/zuul/.ansible/tmp/ansible-local-8450zztissx4/ansible-tmp-1567664814.2179358-150200870655143/AnsiballZ_eos_system.py", line 116, in <module>
_ansiballz_main()
File "/home/zuul/.ansible/tmp/ansible-local-8450zztissx4/ansible-tmp-1567664814.2179358-150200870655143/AnsiballZ_eos_system.py", line 108, in _ansiballz_main
invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS)
File "/home/zuul/.ansible/tmp/ansible-local-8450zztissx4/ansible-tmp-1567664814.2179358-150200870655143/AnsiballZ_eos_system.py", line 54, in invoke_module
runpy.run_module(mod_name='ansible.modules.network.eos.eos_system', init_globals=None, run_name='__main__', alter_sys=False)
File "/usr/lib64/python3.7/runpy.py", line 208, in run_module
return _run_code(code, {}, init_globals, run_name, mod_spec)
File "/usr/lib64/python3.7/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/tmp/ansible_eos_system_payload_lj5nlld1/ansible_eos_system_payload.zip/ansible/modules/network/eos/eos_system.py", line 339, in <module>
File "/tmp/ansible_eos_system_payload_lj5nlld1/ansible_eos_system_payload.zip/ansible/modules/network/eos/eos_system.py", line 322, in main
File "/tmp/ansible_eos_system_payload_lj5nlld1/ansible_eos_system_payload.zip/ansible/modules/network/eos/eos_system.py", line 260, in map_config_to_obj
File "/tmp/ansible_eos_system_payload_lj5nlld1/ansible_eos_system_payload.zip/ansible/module_utils/network/eos/eos.py", line 632, in get_config
File "/tmp/ansible_eos_system_payload_lj5nlld1/ansible_eos_system_payload.zip/ansible/module_utils/network/eos/eos.py", line 107, in get_connection
File "/tmp/ansible_eos_system_payload_lj5nlld1/ansible_eos_system_payload.zip/ansible/module_utils/connection.py", line 185, in __rpc__
ansible.module_utils.connection.ConnectionError: the JSON object must be str, bytes or bytearray, not list
```
| https://github.com/ansible/ansible/issues/61869 | https://github.com/ansible/ansible/pull/62350 | 5cd3be9129c81388c213bcd6b5de7741b9eee8c4 | 84d9b3e58986d70ca64539e816e342a9d7d0b888 | 2019-09-05T16:17:32Z | python | 2019-09-17T14:00:19Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,844 | ["lib/ansible/module_utils/network/iosxr/config/l3_interfaces/l3_interfaces.py", "test/integration/targets/iosxr_l3_interfaces/tests/cli/rtt.yaml"] | IOSXR L3 is having idempotent issue | <!--- Verify first that your issue is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
<!--- Explain the problem briefly below -->
IOSXR L3 is having idempotent issue, which is resulting into change as True even if there's no change.
https://dashboard.zuul.ansible.com/t/ansible/build/40e9d4f8d8f04e53a06f7b07849aa304
https://dashboard.zuul.ansible.com/t/ansible/build/2447ad82cf5c475c8f5c2c4546ca18f6
https://dashboard.zuul.ansible.com/t/ansible/build/52237d4c64644a1fb18e941b5da75bb8
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
<!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure -->
iosxr_l3_interfaces
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
2.9 and devel
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
ios
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
<!--- Paste example playbooks or commands between quotes below -->
```yaml
```
<!--- HINT: You can paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
On the second run of play, the run should be idempotent
##### ACTUAL RESULTS
<!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) -->
On the second run of play, the run is not idempotent
<!--- Paste verbatim command output between quotes -->
```paste below
```
| https://github.com/ansible/ansible/issues/61844 | https://github.com/ansible/ansible/pull/61860 | 375eb9723aed60b121531a4b5134f50fada465ba | 1425d2351397b3b4f442ba42d59f0ceb6516017e | 2019-09-05T13:20:52Z | python | 2019-09-05T20:39:15Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,833 | ["lib/ansible/modules/source_control/gitlab_hook.py"] | gitlab_hook module doesn't have parameter "trigger by comment" | <!--- Verify first that your feature was not already discussed on GitHub -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
<!--- Describe the new feature/improvement briefly below -->
In gitlab_hook module doesn't have parameter "Comment" which is necessary for my DevOps flow and generally very useful for triggering a job. Without this option, I and a lot of people cannot use this module fully.
##### ISSUE TYPE
- Feature Idea
##### COMPONENT NAME
<!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure -->
https://docs.ansible.com/ansible/latest/modules/gitlab_hook_module.html
##### ADDITIONAL INFORMATION
<!--- Describe how the feature would be used, why it is needed and what it would solve -->
1. I use the newest version of ansible.
2. It's about this option in gitlab:
[](https://postimg.cc/sGYMgjkG)
<!--- Paste example playbooks or commands between quotes below -->
```yaml
```
<!--- HINT: You can also paste gist.github.com links for larger files -->
| https://github.com/ansible/ansible/issues/61833 | https://github.com/ansible/ansible/pull/61837 | e06dbe6e4f925b473acf0d03deda3b6d780a9dd3 | 223dab99ea0075c96bf5bd049d2a140de5b4a285 | 2019-09-05T08:28:07Z | python | 2019-09-05T11:39:59Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,819 | ["lib/ansible/plugins/connection/network_cli.py"] | eos tests: AttributeError: 'NoneType' object has no attribute 'endswith' | <!--- Verify first that your issue is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
We seem to be having an issue with eos testing and AttributeError: 'NoneType' object has no attribute 'endswith'.
https://object-storage-ca-ymq-1.vexxhost.net/v1/a0b4156a37f9453eb4ec7db5422272df/ansible_79/61779/2a3bc59e39230ad945d42da08a8aad3f91dee027/third-party-check/ansible-test-network-integration-eos-python37/52a7e42/controller/ansible-debug.html#l48225
It looks like self._get_prompt() is None.
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
<!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure -->
eos_logging
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
<!--- Paste example playbooks or commands between quotes below -->
```yaml
zuul.ansible.com
```
<!--- HINT: You can paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
##### ACTUAL RESULTS
<!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) -->
<!--- Paste verbatim command output between quotes -->
```paste below
2019-09-04 20:16:25,014 p=zuul u=31800 | Traceback (most recent call last):
File "/home/zuul/src/github.com/ansible/ansible/lib/ansible/utils/jsonrpc.py", line 45, in handle_request
result = rpc_method(*args, **kwargs)
File "/home/zuul/src/github.com/ansible/ansible/lib/ansible/plugins/connection/network_cli.py", line 389, in update_play_context
self._terminal.on_become(passwd=auth_pass)
File "/home/zuul/src/github.com/ansible/ansible/lib/ansible/plugins/terminal/eos.py", line 62, in on_become
if self._get_prompt().endswith(b'#'):
AttributeError: 'NoneType' object has no attribute 'endswith'
```
| https://github.com/ansible/ansible/issues/61819 | https://github.com/ansible/ansible/pull/61797 | 394a05108dc79efc8d917fa0febbfcf721e94b61 | a365e77cc350ff5ce2dfaf421d7a3f54152cf187 | 2019-09-04T23:14:41Z | python | 2019-09-05T18:48:16Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,804 | ["lib/ansible/modules/cloud/azure/azure_rm_virtualmachinescaleset.py"] | azure_rm_virtualmachinescaleset module fails to create a VMSS when data disks are specified in custom image | <!--- Verify first that your issue is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
<!--- Explain the problem briefly below -->
The Ansible azure_rm_virtualmachinescaleset module fails to create a VMSS when data disks are specified, and the source for the VM is a custom image which also has exactly the same disk profile specified.
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
<!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure -->
azure_rm_virtualmachinescaleset
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
ansible 2.8.2
config file = /etc/ansible/ansible.cfg
configured module search path = [u'/home/someuser/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python2.7/site-packages/ansible
executable location = /usr/bin/ansible
python version = 2.7.5 (default, Jun 20 2019, 20:27:34) [GCC 4.8.5 20150623 (Red Hat 4.8.5-36)]
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
-- No output --
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
CentOS 7.5
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
1. Create a CentOS VM with 1 attached data disk (Standard_LRS) of size 1GB
2. Capture an image of the above VM using steps like [this](https://docs.microsoft.com/en-us/azure/virtual-machines/linux/capture-image)
3. Run an Ansible playbook like below to create a VMSS based on the above custom image
<!--- Paste example playbooks or commands between quotes below -->
```yaml
- name: create a VMSS
hosts: localhost
connection: local
tasks:
- name: Create luns dictionary
set_fact:
luns_dict: "{{ luns_dict | default ([]) + [{ 'lun': item, 'managed_disk_type': Standard_LRS, 'disk_size_gb': 1 , 'caching': None } ] }}"
with_sequence: start=0 end=1
- name: Create Scale Set
azure_rm_virtualmachinescaleset:
resource_group: "azure_rg"
location: "westus2"
name: "somevmss"
vm_size: "Standard_D3_v2"
admin_username: "someuser"
ssh_password_enabled: false
ssh_public_keys:
- path: /home/someuser/.ssh/authorized_keys
key_data: "{{ lookup('file', '~/.ssh/id_rsa.pub') }}"
capacity: 2
virtual_network_name: "vnet1"
subnet_name: "subnet1"
upgrade_policy: Manual
tier: Standard
managed_disk_type: "Standard_LRS"
os_disk_caching: ReadWrite
enable_accelerated_networking: yes
image:
resource_group: "somergwithimage"
name: "someimg"
data_disks: "{{ luns_dict }}"
```
<!--- HINT: You can paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
VMSS is created successfully with the data disks from the image.
##### ACTUAL RESULTS
<!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) -->
Get error message as below when trying to create from Ansible:
<!--- Paste verbatim command output between quotes -->
```paste below
"msg": "Error creating or updating virtual machine somevmss - Azure Error: InvalidParameter\nMessage: Cannot specify user image overrides for a disk already defined in the specified image reference.\nTarget: storageProfile"
```
Note that creating a VMSS from the same image using Azure CLI succeeds; sample command below:
```
az vmss create -n vmss_2 --admin-username azureadmin --admin-password somepass -g some-rg --instance-count 4 --image someimgresourceid --location westus2 --vnet-name vnet1 --subnet subnet1 --subnet-address-prefix 10.1.0.0/16 --vnet-address-prefix 10.0.0.0/8 --vm-sku Standard_D4s_v3 --storage-sku os=Premium_LRS 1=Standard_LRS
``` | https://github.com/ansible/ansible/issues/61804 | https://github.com/ansible/ansible/pull/62357 | 36def8bf03b7d954c79bd53f690105a40c2b9bd3 | 23995fef48568412e91739a58f12e4a6b309bd54 | 2019-09-04T18:40:12Z | python | 2020-02-20T07:19:48Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,780 | ["docs/docsite/rst/network/dev_guide/developing_resource_modules_network.rst", "docs/docsite/rst/network/dev_guide/index.rst"] | Add documentation for the network resource model builder | <!--- Verify first that your improvement is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
<!--- Explain the problem briefly below, add suggestions to wording or structure -->
Add how to use the resource model builder to the network developer guide.
<!--- HINT: Did you know the documentation has an "Edit on GitHub" link on every page ? -->
##### ISSUE TYPE
- Documentation Report
##### COMPONENT NAME
<!--- Write the short name of the rst file, module, plugin, task or feature below, use your best guess if unsure -->
docs.ansible.com
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. OS version, browser, etc. -->
##### ADDITIONAL INFORMATION
<!--- Describe how this improves the documentation, e.g. before/after situation or screenshots -->
<!--- HINT: You can paste gist.github.com links for larger files -->
| https://github.com/ansible/ansible/issues/61780 | https://github.com/ansible/ansible/pull/62222 | fbf182c3690d54de98e722c90e5f6ce273ffccba | b17581a3075f571ed5b48126282e086a6efa30cc | 2019-09-04T15:15:25Z | python | 2019-09-23T15:10:05Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,773 | ["lib/ansible/module_utils/network/junos/config/interfaces/interfaces.py", "lib/ansible/module_utils/network/junos/config/l2_interfaces/l2_interfaces.py", "lib/ansible/module_utils/network/junos/config/l3_interfaces/l3_interfaces.py", "lib/ansible/module_utils/network/junos/config/lacp/lacp.py", "lib/ansible/module_utils/network/junos/config/lacp_interfaces/lacp_interfaces.py", "lib/ansible/module_utils/network/junos/config/lag_interfaces/lag_interfaces.py", "lib/ansible/module_utils/network/junos/config/lldp_global/lldp_global.py", "lib/ansible/module_utils/network/junos/config/lldp_interfaces/lldp_interfaces.py", "lib/ansible/module_utils/network/junos/config/vlans/vlans.py", "test/integration/targets/junos_l3_interfaces/tests/netconf/junos_l3_interfaces.yml"] | junos resource modules are documented with parameter `commands` but use the return value `xml` | ##### SUMMARY
in the module documentation we have the return value set to `before` and `after` and `commands` for all resource modules. At some point this changed for only junos resource modules, and only for the parameter `commands`. It has been changed to `xml`. I think this *should* be *commands* and just return the xml payload under the variable named *commands*
this file can be found here: https://github.com/ansible/ansible/blob/devel/lib/ansible/module_utils/network/junos/config/l2_interfaces/l2_interfaces.py#L80
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
junos_l3_interfaces
junos_l2_interfaces
probably all junos resource modules
##### ANSIBLE VERSION
```paste below
latest dev
```
##### CONFIGURATION
```paste below
DEFAULT_HOST_LIST(/home/student1/.ansible.cfg) = [u'/home/student1/networking-workshop/lab_inventory/hosts']
DEFAULT_STDOUT_CALLBACK(/home/student1/.ansible.cfg) = yaml
DEFAULT_TIMEOUT(/home/student1/.ansible.cfg) = 60
DEPRECATION_WARNINGS(/home/student1/.ansible.cfg) = False
HOST_KEY_CHECKING(/home/student1/.ansible.cfg) = False
PERSISTENT_COMMAND_TIMEOUT(/home/student1/.ansible.cfg) = 60
PERSISTENT_CONNECT_TIMEOUT(/home/student1/.ansible.cfg) = 60
RETRY_FILES_ENABLED(/home/student1/.ansible.cfg) = False
```
##### OS / ENVIRONMENT
RHEL 7.6
##### STEPS TO REPRODUCE
```yaml
[student1@ansible ~]$ cat junos.yml
---
- hosts: rtr3
gather_facts: false
tasks:
- name: grab info
junos_facts:
gather_subset: min
gather_network_resources: l3_interfaces
- debug:
var: ansible_network_resources
```
<!--- HINT: You can paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
the variable `commands` would return the payload versus the variable named `xml` that is not documented
like this
```
TASK [ensure that the IP address information is accurate] ***********************************************************************
[WARNING]: Platform linux on host rtr3 is using the discovered Python interpreter at /usr/bin/python, but future installation
of another Python interpreter could change this. See
https://docs.ansible.com/ansible/devel/reference_appendices/interpreter_discovery.html for more information.
changed: [rtr3] => changed=true
after:
- name: lo0
unit: '0'
ansible_facts:
discovered_interpreter_python: /usr/bin/python
before:
- ipv4:
- address: 10.10.10.1/24
ipv6:
- address: fc00::100/64
- address: fc00::101/64
name: lo0
unit: '0'
commands:
- <nc:interfaces xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0"><nc:interface><nc:name>lo0</nc:name><nc:unit><nc:name>0</nc:name><nc:family><nc:inet><nc:address delete="delete"/></nc:inet><nc:inet6><nc:address delete="delete"/></nc:inet6></nc:family></nc:unit></nc:interface></nc:interfaces>
```
##### ACTUAL RESULTS
<!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) -->
<!--- Paste verbatim command output between quotes -->
```paste below
TASK [ensure that the IP address information is accurate] ***********************************************************************
[WARNING]: Platform linux on host rtr3 is using the discovered Python interpreter at /usr/bin/python, but future installation
of another Python interpreter could change this. See
https://docs.ansible.com/ansible/devel/reference_appendices/interpreter_discovery.html for more information.
changed: [rtr3] => changed=true
after:
- name: lo0
unit: '0'
ansible_facts:
discovered_interpreter_python: /usr/bin/python
before:
- ipv4:
- address: 10.10.10.1/24
ipv6:
- address: fc00::100/64
- address: fc00::101/64
name: lo0
unit: '0'
xml:
- <nc:interfaces xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0"><nc:interface><nc:name>lo0</nc:name><nc:unit><nc:name>0</nc:name><nc:family><nc:inet><nc:address delete="delete"/></nc:inet><nc:inet6><nc:address delete="delete"/></nc:inet6></nc:family></nc:unit></nc:interface></nc:interfaces>
```
| https://github.com/ansible/ansible/issues/61773 | https://github.com/ansible/ansible/pull/62041 | 6fb1d56fdc022cb6001539ea4bbc87d759093987 | ff53ca76b83d151fb05ba0c69def6089dc893135 | 2019-09-04T14:10:24Z | python | 2019-09-11T05:36:08Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,758 | ["docs/docsite/rst/user_guide/playbooks_conditionals.rst"] | Conditionals documentation should explicitly define what operators are supported | ##### SUMMARY
The current documentation page for Conditionals and the 'when' clause only imples what the supported comparison operators are. For clarity, the supported operators should be explicitly documented.
##### ISSUE TYPE
- Documentation Report
##### COMPONENT NAME
user_guide/playbooks_conditionals.html
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. OS version, browser, etc. -->
##### ADDITIONAL INFORMATION
<!--- Describe how this improves the documentation, e.g. before/after situation or screenshots -->
<!--- HINT: You can paste gist.github.com links for larger files -->
| https://github.com/ansible/ansible/issues/61758 | https://github.com/ansible/ansible/pull/61814 | 6cc326dcf19942a7567964f9855389ef34984939 | b625b430f1f27d350bd6347c4692361566344e03 | 2019-09-04T09:27:43Z | python | 2020-02-14T15:53:14Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,738 | ["changelogs/fragments/61738-ecs-certificate-invalid-chain.yaml", "lib/ansible/modules/crypto/entrust/ecs_certificate.py", "test/integration/targets/ecs_certificate/tasks/main.yml", "test/integration/targets/ecs_certificate/vars/main.yml"] | ecs_certificate chain not in standard format | ##### SUMMARY
The file contents that end up as the output of ecs_certificates "full_chain_path" are not a valid format for import into, for example, a PKCS12 store.
This is the result of the return value of the ECS API being an array, and not properly turning that array into concatenated certificates for the resulting PEM file.
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
ecs_certificate
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
Applies to ansible 2.9.0.dev0
##### CONFIGURATION
N/A affects all configurations
##### OS / ENVIRONMENT
N/A affects all OS/environment
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
Populate full_chain_path and inspect output
##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
A properly formatted PEM certificate chain
##### ACTUAL RESULTS
A certificate chain in format ['CERT','CERT']
| https://github.com/ansible/ansible/issues/61738 | https://github.com/ansible/ansible/pull/61858 | cac93cbd1f041eac5045250a6663644cdbba3df8 | 943888b9553bca40b18c3922f508645d09f53392 | 2019-09-03T20:47:14Z | python | 2019-09-07T05:58:25Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,719 | ["lib/ansible/module_utils/network/eos/providers/module.py", "lib/ansible/module_utils/network/frr/providers/module.py", "lib/ansible/module_utils/network/ios/providers/module.py", "lib/ansible/module_utils/network/iosxr/providers/module.py"] | eos_bgp / ios_bgp / iosxr_bgp not safe for collection | <!--- Verify first that your issue is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
All 3 of these providers, do not work properly when converted to a collection. The following error is raise:
could not find a suitable provider for this module
https://object-storage-ca-ymq-1.vexxhost.net/v1/a0b4156a37f9453eb4ec7db5422272df/ansible_20/20/30f1a39eece8bc37eeb89f05d733d133c707626e/check/ansible-test-network-integration-eos-python27/ca018b0/controller/ara-report/
https://object-storage-ca-ymq-1.vexxhost.net/v1/a0b4156a37f9453eb4ec7db5422272df/ansible_15/15/2b0be560d30c4c24620b0ade29bd62b7fbb57b22/check/ansible-test-network-integration-ios-python37/a516d70/controller/ara-report/
https://object-storage-ca-ymq-1.vexxhost.net/v1/a0b4156a37f9453eb4ec7db5422272df/ansible_15/15/2019f0b07076ca58ddb9e9ac0be65402b477eec1/check/ansible-test-network-integration-iosxr-python27/38b49a0/controller/ara-report/
This appears to be related to how we look up the module / provider for bgp tasks.
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
<!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure -->
eos_bgp
ios_bgp
iosxr_bgp
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
ansible stable-2.9
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
zuul.ansible.com
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
git clone any one of the collections below, then run ansible-test network integration testing.
<!--- Paste example playbooks or commands between quotes below -->
```yaml
https://github.com/ansible-network/ansible_collections.arista.eos
https://github.com/ansible-network/ansible_collections.cisco.ios
https://github.com/ansible-network/ansible_collections.cisco.iosxr
```
<!--- HINT: You can paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
##### ACTUAL RESULTS
<!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) -->
<!--- Paste verbatim command output between quotes -->
```paste below
2019-08-31 03:48:50,568 p=zuul u=5694 | <74.63.204.64> EXEC /bin/sh -c 'rm -f -r /home/zuul/.ansible/tmp/ansible-local-5510omNavF/ansible-tmp-1567223329.55-30831165844767/ > /dev/null 2>&1 && sleep 0'
2019-08-31 03:48:50,581 p=zuul u=5510 | The full traceback is:
WARNING: The below traceback may *not* be related to the actual failure.
File "/tmp/ansible_arista.eos.eos_bgp_payload_qprZAR/ansible_arista.eos.eos_bgp_payload.zip/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/module.py", line 63, in edit_config
commands = self.provider.edit_config(current_config)
File "/tmp/ansible_arista.eos.eos_bgp_payload_qprZAR/ansible_arista.eos.eos_bgp_payload.zip/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/module.py", line 36, in provider
cls = providers.get(network_os, self._name, connection_type)
File "/tmp/ansible_arista.eos.eos_bgp_payload_qprZAR/ansible_arista.eos.eos_bgp_payload.zip/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/providers.py", line 44, in get
raise ValueError("could not find a suitable provider for this module")
2019-08-31 03:48:50,587 p=zuul u=5510 | fatal: [eos-4.20.10]: FAILED! => changed=false
invocation:
module_args:
config:
address_family: null
bgp_as: 64496
log_neighbor_changes: null
neighbors: null
networks: null
redistribute: null
router_id: 192.0.2.2
operation: merge
msg: could not find a suitable provider for this module
```
| https://github.com/ansible/ansible/issues/61719 | https://github.com/ansible/ansible/pull/61761 | 9ee0deea24e04b5221edec74c74da922a2544a29 | a795f6941eb50c9e21ff20c297700c1e264223b5 | 2019-09-03T16:11:56Z | python | 2019-09-04T14:29:00Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,698 | ["changelogs/fragments/61740-docker_container-port-range-parsing.yml", "lib/ansible/modules/cloud/docker/docker_container.py"] | Impossible to omit or pass a default value to published_ports on docker_container | ##### SUMMARY
Hi,
When you want to pass an empty list or a null/None value to published_ports on docker_container it's actually impossible, so you get this error
```
File \"/tmp/ansible_docker_container_payload_ZOZc5l/__main__.py\", line 1448, in _parse_publish_ports\r\n File \"/tmp/ansible_docker_container_payload_ZOZc5l/__main__.py\", line 1003, in parse_port_range\r\nValueError: invalid literal for int() with base 10: ''\r\n",
```
Ref #61602
The problem is that we parse via `_parse_publish_ports` the parameter if self.published_ports is not None or not 'all'
Also after that there is no control on each elements of the list, (not like for the volumes parameter by example)
So I propose to patch line 1151
`self.published_ports = self._parse_publish_ports() `
to
`self.published_ports = self._parse_publish_ports() if self.published_ports else None`
Best regards
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
* docker_container
##### ANSIBLE VERSION
```
ansible 2.8.4
``` | https://github.com/ansible/ansible/issues/61698 | https://github.com/ansible/ansible/pull/61740 | 943888b9553bca40b18c3922f508645d09f53392 | d40ba28fb43a15eac0c604647e6535fb8fba4939 | 2019-09-03T07:53:49Z | python | 2019-09-08T18:30:18Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,687 | ["lib/ansible/modules/cloud/amazon/s3_bucket.py", "test/integration/targets/s3_bucket/tasks/main.yml"] | s3_bucket, aws:kms encryption does not default to default s3 key | ##### SUMMARY
The documentation states the following:
```
encryption_key_id
KMS master key ID to use for the default encryption. This parameter is allowed if encryption is aws:kms. If not specified then it will default to the AWS provided KMS key.
```
However, omitting the variable yields the following:
```{"changed": false, "msg": "encryption is aws:kms but all of the following are missing: encryption_key_id"}```
due to these lines: https://github.com/ansible/ansible/blob/devel/lib/ansible/modules/cloud/amazon/s3_bucket.py#L703-L704 .
Alternatively, specifying an empty string as key yields the following botocore exception:
``` "error": {
"code": "InvalidArgument",
"message": "if the default sse algorithm is aws:kms and a KMSMasterKeyID is specified, it must be non-empty",
"argument_name": "ApplyServerSideEncryptionByDefault"
},```
Specifying any other value will attempt to set the name of the key to that value.
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
s3_bucket
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
ansible 2.10.0.dev0
config file = /deploy-data/ansible-deploy/ansible.cfg
configured module search path = ['/deploy-data/ansible-deploy/library']
ansible python module location = /var/lib/awx/venv/ansible/lib/python3.6/site-packages/ansible
executable location = /var/lib/awx/venv/ansible/bin/ansible
python version = 3.6.8 (default, Jan 14 2019, 11:02:34) [GCC 8.0.1 20180414 (experimental) [trunk revision 259383]]
```
This also applies to 2.9.0.dev0
##### OS / ENVIRONMENT
N/A
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
<!--- Paste example playbooks or commands between quotes below -->
```yaml
- s3_bucket: This errors out because empty strings cannot be used
name: "{{ bucket_name }}"
region: "{{ region }}"
encryption: "aws:kms"
encryption_key_id: ""
- s3_bucket: This errors out due to the key not being set
name: "{{ bucket_name }}"
region: "{{ region }}"
encryption: "aws:kms"
- name: This sets the key used to one named 'False'
s3_bucket:
name: "{{ bucket_name }}"
region: "{{ region }}"
encryption: "aws:kms"
encryption_key_id: False
```
##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
As per the documented changes, it would be expected that the default S3 KMS would be applied to the bucket.
##### ACTUAL RESULTS
See above. | https://github.com/ansible/ansible/issues/61687 | https://github.com/ansible/ansible/pull/62031 | 2e81b813ddfdd0b37c0d5fad34ec061c6f0eb079 | aa68f728fdd9b2b93da3da6a6b18a00b24cfe7e3 | 2019-09-02T14:08:59Z | python | 2019-10-21T23:45:41Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,685 | ["lib/ansible/modules/monitoring/grafana_dashboard.py"] | Folder support for grafana_dashboard | ##### SUMMARY
When creating a dashboard, I'd like to assign it to a folder in Grafana.
##### ISSUE TYPE
- Feature Idea
##### COMPONENT NAME
`grafana_dashboard`
##### ADDITIONAL INFORMATION
<!--- Describe how the feature would be used, why it is needed and what it would solve -->
Folders in Grafana are used for ACL etc.. When no folder is referenced, the dashboard ends up in the default folder (and can't be moved as it's managed outside of Grafana).
Here's the API related to creating/updating dashboards:
https://grafana.com/docs/http_api/dashboard/
The relevant bit is `folderId`.
For context, here's the folder API (probably a concern for a different module — `grafana_folder`):
https://grafana.com/docs/http_api/folder/
I'd propose something like this and then map `folder_id` to `folderId`. The default is a value of `0`. And then dashboards end up in "General".
<!--- Paste example playbooks or commands between quotes below -->
```yaml
- hosts: localhost
connection: local
tasks:
- name: Import Grafana dashboard
grafana_dashboard:
grafana_url: http://localhost:3000
grafana_api_key: "{{ grafana_api_key }}"
state: present
folder_id: 0
message: Updated by ansible
overwrite: yes
path: /path/to/mydashboard.json
```
As an additional motivation, I'm a user of a Grafana role. They are planning to deprecate their dashboard management in favour of this module.
Related: https://github.com/cloudalchemy/ansible-grafana/issues/174 | https://github.com/ansible/ansible/issues/61685 | https://github.com/ansible/ansible/pull/63342 | 7d9a0baa7f934f2995d9207d84bf1647f81506b1 | 0b9c241822061e77d0df4b5141befaa725d6594a | 2019-09-02T12:08:39Z | python | 2019-10-18T09:35:56Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,681 | ["docs/docsite/rst/scenario_guides/guide_kubernetes.rst"] | Kubernetes scenario guide out of date | <!--- Verify first that your improvement is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
<!--- Explain the problem briefly below, add suggestions to wording or structure -->
This scenario guide is out of date: https://docs.ansible.com/ansible/latest/scenario_guides/guide_kubernetes.html
It refers to a requirement to use a manually built version of ansible and links to galaxy roles ( https://galaxy.ansible.com/ansible/kubernetes-modules ) that exist but are out of date and their source repository ( https://github.com/ansible/ansible-kubernetes-modules ) has been archived, because these modules are now available in ansible itself since Ansible 2.5.
My suggestion would be to remove this file entirely as it's no-longer required in currently supported versions of ansible; Or perhaps replace it with a short page containing a link to the k8s_raw and openshift_raw modules that were added to Ansible 2.5.
##### ISSUE TYPE
- Documentation Report
##### COMPONENT NAME
guide_kubernetes.rst
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
N/A - entire page out of date for ansible >= 2.5
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
N/A - entire page out of date for ansible >= 2.5
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. OS version, browser, etc. -->
##### ADDITIONAL INFORMATION
<!--- Describe how this improves the documentation, e.g. before/after situation or screenshots -->
I found this documentation via a search in the sidebar of the docs site. After reading and following the links I realised that I should disregard it for modern versions of ansible. Simply not having the page there would be an improvement.
<!--- HINT: You can paste gist.github.com links for larger files -->
| https://github.com/ansible/ansible/issues/61681 | https://github.com/ansible/ansible/pull/71372 | 5498b0bb7182d59996fedbfa39a4d3fa825f2305 | 59b80b9146765382f7fbbeefe401fe33b0df033b | 2019-09-02T11:14:12Z | python | 2020-08-21T14:37:03Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,672 | ["lib/ansible/module_utils/urls.py", "lib/ansible/modules/web_infrastructure/jenkins_plugin.py", "lib/ansible/modules/web_infrastructure/jenkins_script.py"] | jenkins_plugin: use of authorization crumb must be conducted in a session since LTS 2.176 | <!--- Verify first that your issue is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
Plugins cannot be installed using the jenkins_plugin module since upgrading to LTS 2.176. This is due to additional CSRF security where the crumb that is issued may only be used within the same session.
In the jenkins log messages like this are reported:
```
WARNING: Found invalid crumb 5cae269d58b83057dfbd85f6c32f0845. Will check remaining parameters for a valid one...
```
The module will then error with `Cannot install plugin.`
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
jenkins_plugin
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```
ansible 2.8.4
config file = /etc/ansible/ansible.cfg
configured module search path = [u'/home/james/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python2.7/dist-packages/ansible
executable location = /usr/bin/ansible
python version = 2.7.16 (default, Apr 6 2019, 01:42:57) [GCC 8.3.0]
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
(no output)
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
Install jenkins 2.176, attempt to install plugins using ansible, e.g. a task such as:
```
- name: "Install Jenkins plugins"
jenkins_plugin:
owner: jenkins
group: jenkins
name: "{{ item }}"
url: "https://{{ ansible_host }}:8090/"
url_username: "{{ ansible_user }}"
url_password: "{{ ansible_become_pass }}"
force_basic_auth: yes
with_items:
- ansicolor
```
<!--- Paste example playbooks or commands between quotes below -->
```yaml
```
<!--- HINT: You can paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
The named plugin is installed in jenkins.
##### ACTUAL RESULTS
<!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) -->
<!--- Paste verbatim command output between quotes -->
```paste below
```
| https://github.com/ansible/ansible/issues/61672 | https://github.com/ansible/ansible/pull/61673 | dfc023209fc7460c449b2e97feb1b5e6d79d1491 | 76b5b90bd6fdf4ac3fb785f81c5fab18445db2e2 | 2019-09-02T09:46:51Z | python | 2019-09-10T13:44:37Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,624 | ["changelogs/fragments/61624-fix-galaxy-url-building.yml", "lib/ansible/galaxy/api.py"] | ansible-galaxy 2.9 role install truncates API URL | <!--- Verify first that your issue is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
When trying to install a role, install fails and the role is not found. Investigation shows the role API URL being used to lookup the role information is being truncated in `lib/ansible/galaxy/api.py` line 274, potentially due to the change from `rstrip()` to `strip()` in `_urljoin()`.
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
<!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure -->
ansible-galaxy
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
ansible 2.9.0b1
config file = /etc/ansible/ansible.cfg
configured module search path = ['/home/calvin/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /home/calvin/projects/ansible/lib/ansible
executable location = /home/calvin/.local/share/virtualenvs/orion/bin/ansible
python version = 3.6.9 (default, Jul 3 2019, 17:57:57) [GCC 8.3.1 20190223 (Red Hat 8.3.1-2)]
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
<!--- Paste example playbooks or commands between quotes below -->
```yaml
```
- Try to install any role from Galaxy
<!--- HINT: You can paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
The role to be located and installed from Galaxy
##### ACTUAL RESULTS
<!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) -->
The role is not found, even though it clearly exists.
<!--- Paste verbatim command output between quotes -->
```paste below
(orion) [calvin@localhost ansible]$ ansible-galaxy install geerlingguy.nginx
- downloading role 'nginx', owned by geerlingguy
[WARNING]: - geerlingguy.nginx was NOT installed successfully: - sorry, geerlingguy.nginx was not found on https://galaxy.ansible.com.
```
Additional evidence of where the problem comes from internally:
```
(orion) [calvin@localhost ansible]$ ansible-galaxy -vvv install --server=http://galaxy.ansible.com geerlingguy.docker
[DEPRECATION WARNING]: Setting verbosity before the arg sub command is deprecated, set the verbosity after the sub command. This feature will be
removed in version 2.13. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.
ansible-galaxy 2.9.0b1
config file = /etc/ansible/ansible.cfg
configured module search path = ['/home/calvin/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /home/calvin/projects/ansible/lib/ansible
executable location = /home/calvin/.local/share/virtualenvs/orion/bin/ansible-galaxy
python version = 3.6.9 (default, Jul 3 2019, 17:57:57) [GCC 8.3.1 20190223 (Red Hat 8.3.1-2)]
Using /etc/ansible/ansible.cfg as config file
Processing role geerlingguy.docker
- downloading role 'docker', owned by geerlingguy
> /home/calvin/projects/ansible/lib/ansible/galaxy/api.py(274)lookup_role_by_name()
-> url = _urljoin(self.api_server, self.available_api_versions['v1'], "roles",
(Pdb) l
269 display.display("- downloading role '%s', owned by %s" % (role_name, user_name))
270 except Exception:
271 raise AnsibleError("Invalid role name (%s). Specify role as format: username.rolename" % role_name)
272
273 import pdb; pdb.set_trace()
274 -> url = _urljoin(self.api_server, self.available_api_versions['v1'], "roles",
275 "?owner__username=%s&name=%s" % (user_name, role_name))[:-1]
276 data = self._call_galaxy(url)
277 if len(data["results"]) != 0:
278 return data["results"][0]
279 return None
(Pdb) n
> /home/calvin/projects/ansible/lib/ansible/galaxy/api.py(275)lookup_role_by_name()
-> "?owner__username=%s&name=%s" % (user_name, role_name))[:-1]
(Pdb) n
> /home/calvin/projects/ansible/lib/ansible/galaxy/api.py(276)lookup_role_by_name()
-> data = self._call_galaxy(url)
(Pdb) !url
'https://galaxy.ansible.com/api/v1/roles/?owner__username=geerlingguy&name=docke'
```
Note the truncated URL on the last line of this snippet | https://github.com/ansible/ansible/issues/61624 | https://github.com/ansible/ansible/pull/61775 | adfaefb7321616da2975c95c87a4973d77aea5c4 | 8214d188cf330477ef4e4c2f3cc38826fc5b652c | 2019-08-30T19:08:12Z | python | 2019-09-04T21:06:42Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,616 | [".github/RELEASE_NAMES.yml", "docs/docsite/rst/dev_guide/testing/sanity/release-names.rst", "lib/ansible/release.py", "test/sanity/code-smell/release-names.json", "test/sanity/code-smell/release-names.py"] | 2.10 needs more Led |
##### SUMMARY
The codename for 2.10 needs to be recorded in lib/ansible/release.py
/cc @jimi-c
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
* lib/ansible/release.py
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
2.10 / devel
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
<!--- Paste example playbooks or commands between quotes below -->
```yaml
```
<!--- HINT: You can paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
##### ACTUAL RESULTS
<!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) -->
<!--- Paste verbatim command output between quotes -->
```paste below
```
| https://github.com/ansible/ansible/issues/61616 | https://github.com/ansible/ansible/pull/61873 | 832e03d932da8e21f265abc4b4df27924d92fb47 | f58899eef7bce5a682a52d33914d644e494ff898 | 2019-08-30T16:58:13Z | python | 2019-09-06T01:36:06Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,615 | ["lib/ansible/plugins/connection/httpapi.py"] | "maximum recursion depth exceeded in __instancecheck__" error in fortios httpapi with the latest devel / stable-2.9 branches | <!--- Verify first that your issue is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
<!--- Explain the problem briefly below -->
When running the latest devel/stable-2.0 branches of Ansible (as 8/30/2019), fortios httpapi failed with message: The error was: ansible.module_utils.connection.ConnectionError: maximum recursion depth exceeded in __instancecheck__
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
<!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure -->
httpapi
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
ansible 2.9.0.dev0
config file = None
configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /usr/local/lib/python3.7/site-packages/ansible
executable location = /usr/local/bin/ansible
python version = 3.7.4 (default, Jul 13 2019, 14:04:11) [GCC 8.3.0]
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
N/A
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
Test with docker:
FROM python:3.7
...
RUN pip3 install git+https://github.com/ansible/ansible.git
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
1. You need a fortigate device or virtual appliance to test it
2. inventories file
[fgt1]
fgt1 ansible_host=192.168.210.11
[fortios:children]
fgt1
[fortios:vars]
ansible_network_os=fortios
ansible_user=admin
ansible_password=fortinet
ansible_become=no
ansible_become_method=disable
ansible_httpapi_use_ssl=true
ansible_httpapi_validate_certs=false
ansible_httpapi_timeout=300
3. playbook, see blow
4. run, for example,
ansible-playbook -i ./inventories/hosts ./test/test_fos_facts_01.yml -e "ansible_python_interpreter=/usr/local/bin/python"
<!--- Paste example playbooks or commands between quotes below -->
```yaml
---
- name: Test FortiOS Facts 01 - with fortios httpapi
hosts: fgt1
connection: httpapi
gather_facts: False
vars:
vdom: "root"
tasks:
- name: gather basic system status facts
fortios_facts:
vdom: "{{ vdom }}"
gather_subset: [{"fact": "system_status_select"}]
```
<!--- HINT: You can paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
the playbook should be able to gather facts from fortios device.
##### ACTUAL RESULTS
<!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) -->
fatal: [192.168.210.11]: FAILED! => {
"changed": false,
"module_stderr": "Traceback (most recent call last):\n File \"/root/.ansible/tmp/ansible-local-7616x_tmou8t/ansible-tmp-1567183621.2818167-276822456078875/AnsiballZ_fortios_facts.py\", line 102, in <module>\n _ansiballz_main()\n File \"/root/.ansible/tmp/ansible-local-7616x_tmou8t/ansible-tmp-1567183621.2818167-276822456078875/AnsiballZ_fortios_facts.py\", line 94, in _ansiballz_main\n invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS)\n File \"/root/.ansible/tmp/ansible-local-7616x_tmou8t/ansible-tmp-1567183621.2818167-276822456078875/AnsiballZ_fortios_facts.py\", line 40, in invoke_module\n runpy.run_module(mod_name='ansible.modules.network.fortios.fortios_facts', init_globals=None, run_name='__main__', alter_sys=False)\n File \"/usr/local/lib/python3.7/runpy.py\", line 208, in run_module\n return _run_code(code, {}, init_globals, run_name, mod_spec)\n File \"/usr/local/lib/python3.7/runpy.py\", line 85, in _run_code\n exec(code, run_globals)\n File \"/tmp/ansible_fortios_facts_payload_cugsx7mm/ansible_fortios_facts_payload.zip/ansible/modules/network/fortios/fortios_facts.py\", line 282, in <module>\n File \"/tmp/ansible_fortios_facts_payload_cugsx7mm/ansible_fortios_facts_payload.zip/ansible/modules/network/fortios/fortios_facts.py\", line 253, in main\n File \"/tmp/ansible_fortios_facts_payload_cugsx7mm/ansible_fortios_facts_payload.zip/ansible/module_utils/network/fortios/facts/facts.py\", line 90, in get_facts\n File \"/tmp/ansible_fortios_facts_payload_cugsx7mm/ansible_fortios_facts_payload.zip/ansible/module_utils/network/fortios/facts/facts.py\", line 81, in get_network_legacy_facts\n File \"/tmp/ansible_fortios_facts_payload_cugsx7mm/ansible_fortios_facts_payload.zip/ansible/module_utils/network/fortios/facts/system/system.py\", line 40, in populate_facts\n File \"/tmp/ansible_fortios_facts_payload_cugsx7mm/ansible_fortios_facts_payload.zip/ansible/module_utils/network/fortios/facts/system/system.py\", line 49, in system_fact\n File \"/tmp/ansible_fortios_facts_payload_cugsx7mm/ansible_fortios_facts_payload.zip/ansible/module_utils/network/fortios/fortios.py\", line 156, in monitor\n File \"/tmp/ansible_fortios_facts_payload_cugsx7mm/ansible_fortios_facts_payload.zip/ansible/module_utils/connection.py\", line 185, in __rpc__\nansible.module_utils.connection.ConnectionError: maximum recursion depth exceeded in __instancecheck__\n",
"module_stdout": "",
"msg": "MODULE FAILURE\nSee stdout/stderr for the exact error",
"rc": 1
}
<!--- Paste verbatim command output between quotes -->
```paste below
root@186cebecf709:/workspaces/fndn_ansible# ansible-playbook -i ./inventories/hosts ./test/test_fos_facts_01.yml -e "ansible_python_interpreter=/usr/local/bin/python" -vvvv
ansible-playbook 2.9.0.dev0
config file = None
configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /usr/local/lib/python3.7/site-packages/ansible
executable location = /usr/local/bin/ansible-playbook
python version = 3.7.4 (default, Jul 13 2019, 14:04:11) [GCC 8.3.0]
No config file found; using defaults
setting up inventory plugins
host_list declined parsing /workspaces/fndn_ansible/inventories/hosts as it did not pass its verify_file() method
auto declined parsing /workspaces/fndn_ansible/inventories/hosts as it did not pass its verify_file() method
Not replacing invalid character(s) "{'.', '1'}" in group name (192.168.210.11)
[DEPRECATION WARNING]: The TRANSFORM_INVALID_GROUP_CHARS settings is set to allow bad characters in group names by default, this will change, but still be user configurable on
deprecation. This feature will be removed in version 2.10. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.
[WARNING]: Invalid characters were found in group names but not replaced, use -vvvv to see details
Not replacing invalid character(s) "{'.', '1'}" in group name (192.168.210.11)
Parsed /workspaces/fndn_ansible/inventories/hosts inventory source with ini plugin
[WARNING]: Found both group and host with same name: 192.168.210.11
Loading callback plugin default of type stdout, v2.0 from /usr/local/lib/python3.7/site-packages/ansible/plugins/callback/default.py
PLAYBOOK: test_fos_facts_01.yml *************************************************************************************************************************************************
Positional arguments: ./test/test_fos_facts_01.yml
verbosity: 4
connection: smart
timeout: 10
become_method: sudo
tags: ('all',)
inventory: ('/workspaces/fndn_ansible/inventories/hosts',)
extra_vars: ('ansible_python_interpreter=/usr/local/bin/python',)
forks: 5
1 plays in ./test/test_fos_facts_01.yml
PLAY [Test FortiOS Facts 01 - with fortios httpapi] *****************************************************************************************************************************
META: ran handlers
TASK [gather basic system status facts] *****************************************************************************************************************************************
task path: /workspaces/fndn_ansible/test/test_fos_facts_01.yml:10
<192.168.210.11> attempting to start connection
<192.168.210.11> using connection plugin httpapi
<192.168.210.11> local domain socket does not exist, starting it
<192.168.210.11> control socket path is /root/.ansible/pc/7662dd71f8
<192.168.210.11> local domain socket listeners started successfully
<192.168.210.11> loaded API plugin for network_os fortios
<192.168.210.11>
<192.168.210.11> local domain socket path is /root/.ansible/pc/7662dd71f8
<192.168.210.11> ESTABLISH LOCAL CONNECTION FOR USER: root
<192.168.210.11> EXEC /bin/sh -c '( umask 77 && mkdir -p "` echo /root/.ansible/tmp/ansible-local-7616x_tmou8t/ansible-tmp-1567183621.2818167-276822456078875 `" && echo ansible-tmp-1567183621.2818167-276822456078875="` echo /root/.ansible/tmp/ansible-local-7616x_tmou8t/ansible-tmp-1567183621.2818167-276822456078875 `" ) && sleep 0'
Using module file /usr/local/lib/python3.7/site-packages/ansible/modules/network/fortios/fortios_facts.py
<192.168.210.11> PUT /root/.ansible/tmp/ansible-local-7616x_tmou8t/tmp_ymij6o2 TO /root/.ansible/tmp/ansible-local-7616x_tmou8t/ansible-tmp-1567183621.2818167-276822456078875/AnsiballZ_fortios_facts.py
<192.168.210.11> EXEC /bin/sh -c 'chmod u+x /root/.ansible/tmp/ansible-local-7616x_tmou8t/ansible-tmp-1567183621.2818167-276822456078875/ /root/.ansible/tmp/ansible-local-7616x_tmou8t/ansible-tmp-1567183621.2818167-276822456078875/AnsiballZ_fortios_facts.py && sleep 0'
<192.168.210.11> EXEC /bin/sh -c '/usr/local/bin/python /root/.ansible/tmp/ansible-local-7616x_tmou8t/ansible-tmp-1567183621.2818167-276822456078875/AnsiballZ_fortios_facts.py && sleep 0'
<192.168.210.11> EXEC /bin/sh -c 'rm -f -r /root/.ansible/tmp/ansible-local-7616x_tmou8t/ansible-tmp-1567183621.2818167-276822456078875/ > /dev/null 2>&1 && sleep 0'
The full traceback is:
Traceback (most recent call last):
File "/root/.ansible/tmp/ansible-local-7616x_tmou8t/ansible-tmp-1567183621.2818167-276822456078875/AnsiballZ_fortios_facts.py", line 102, in <module>
_ansiballz_main()
File "/root/.ansible/tmp/ansible-local-7616x_tmou8t/ansible-tmp-1567183621.2818167-276822456078875/AnsiballZ_fortios_facts.py", line 94, in _ansiballz_main
invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS)
File "/root/.ansible/tmp/ansible-local-7616x_tmou8t/ansible-tmp-1567183621.2818167-276822456078875/AnsiballZ_fortios_facts.py", line 40, in invoke_module
runpy.run_module(mod_name='ansible.modules.network.fortios.fortios_facts', init_globals=None, run_name='__main__', alter_sys=False)
File "/usr/local/lib/python3.7/runpy.py", line 208, in run_module
return _run_code(code, {}, init_globals, run_name, mod_spec)
File "/usr/local/lib/python3.7/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/tmp/ansible_fortios_facts_payload_cugsx7mm/ansible_fortios_facts_payload.zip/ansible/modules/network/fortios/fortios_facts.py", line 282, in <module>
File "/tmp/ansible_fortios_facts_payload_cugsx7mm/ansible_fortios_facts_payload.zip/ansible/modules/network/fortios/fortios_facts.py", line 253, in main
File "/tmp/ansible_fortios_facts_payload_cugsx7mm/ansible_fortios_facts_payload.zip/ansible/module_utils/network/fortios/facts/facts.py", line 90, in get_facts
File "/tmp/ansible_fortios_facts_payload_cugsx7mm/ansible_fortios_facts_payload.zip/ansible/module_utils/network/fortios/facts/facts.py", line 81, in get_network_legacy_facts
File "/tmp/ansible_fortios_facts_payload_cugsx7mm/ansible_fortios_facts_payload.zip/ansible/module_utils/network/fortios/facts/system/system.py", line 40, in populate_facts
File "/tmp/ansible_fortios_facts_payload_cugsx7mm/ansible_fortios_facts_payload.zip/ansible/module_utils/network/fortios/facts/system/system.py", line 49, in system_fact
File "/tmp/ansible_fortios_facts_payload_cugsx7mm/ansible_fortios_facts_payload.zip/ansible/module_utils/network/fortios/fortios.py", line 156, in monitor
File "/tmp/ansible_fortios_facts_payload_cugsx7mm/ansible_fortios_facts_payload.zip/ansible/module_utils/connection.py", line 185, in __rpc__
ansible.module_utils.connection.ConnectionError: maximum recursion depth exceeded in __instancecheck__
fatal: [192.168.210.11]: FAILED! => {
"changed": false,
"module_stderr": "Traceback (most recent call last):\n File \"/root/.ansible/tmp/ansible-local-7616x_tmou8t/ansible-tmp-1567183621.2818167-276822456078875/AnsiballZ_fortios_facts.py\", line 102, in <module>\n _ansiballz_main()\n File \"/root/.ansible/tmp/ansible-local-7616x_tmou8t/ansible-tmp-1567183621.2818167-276822456078875/AnsiballZ_fortios_facts.py\", line 94, in _ansiballz_main\n invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS)\n File \"/root/.ansible/tmp/ansible-local-7616x_tmou8t/ansible-tmp-1567183621.2818167-276822456078875/AnsiballZ_fortios_facts.py\", line 40, in invoke_module\n runpy.run_module(mod_name='ansible.modules.network.fortios.fortios_facts', init_globals=None, run_name='__main__', alter_sys=False)\n File \"/usr/local/lib/python3.7/runpy.py\", line 208, in run_module\n return _run_code(code, {}, init_globals, run_name, mod_spec)\n File \"/usr/local/lib/python3.7/runpy.py\", line 85, in _run_code\n exec(code, run_globals)\n File \"/tmp/ansible_fortios_facts_payload_cugsx7mm/ansible_fortios_facts_payload.zip/ansible/modules/network/fortios/fortios_facts.py\", line 282, in <module>\n File \"/tmp/ansible_fortios_facts_payload_cugsx7mm/ansible_fortios_facts_payload.zip/ansible/modules/network/fortios/fortios_facts.py\", line 253, in main\n File \"/tmp/ansible_fortios_facts_payload_cugsx7mm/ansible_fortios_facts_payload.zip/ansible/module_utils/network/fortios/facts/facts.py\", line 90, in get_facts\n File \"/tmp/ansible_fortios_facts_payload_cugsx7mm/ansible_fortios_facts_payload.zip/ansible/module_utils/network/fortios/facts/facts.py\", line 81, in get_network_legacy_facts\n File \"/tmp/ansible_fortios_facts_payload_cugsx7mm/ansible_fortios_facts_payload.zip/ansible/module_utils/network/fortios/facts/system/system.py\", line 40, in populate_facts\n File \"/tmp/ansible_fortios_facts_payload_cugsx7mm/ansible_fortios_facts_payload.zip/ansible/module_utils/network/fortios/facts/system/system.py\", line 49, in system_fact\n File \"/tmp/ansible_fortios_facts_payload_cugsx7mm/ansible_fortios_facts_payload.zip/ansible/module_utils/network/fortios/fortios.py\", line 156, in monitor\n File \"/tmp/ansible_fortios_facts_payload_cugsx7mm/ansible_fortios_facts_payload.zip/ansible/module_utils/connection.py\", line 185, in __rpc__\nansible.module_utils.connection.ConnectionError: maximum recursion depth exceeded in __instancecheck__\n",
"module_stdout": "",
"msg": "MODULE FAILURE\nSee stdout/stderr for the exact error",
"rc": 1
}
PLAY RECAP **********************************************************************************************************************************************************************
192.168.210.11 : ok=0 changed=0 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0
```
| https://github.com/ansible/ansible/issues/61615 | https://github.com/ansible/ansible/pull/61617 | 447c7d9ff0ae0da185c2bc78e9d33ce30daf1892 | d20d10b5c5d92168708a0803783e5c51da84d0a0 | 2019-08-30T16:52:33Z | python | 2019-09-03T12:55:20Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,609 | ["changelogs/fragments/ansible-galaxy-role-server.yaml", "lib/ansible/cli/galaxy.py", "lib/ansible/galaxy/__init__.py", "lib/ansible/galaxy/role.py"] | ansible-galaxy 2.9 role install ignores --server option | <!--- Verify first that your issue is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
Role install in the current `stable-2.9` branch attempts to install from `http://galaxy.ansible.com/` ignoring anything passed to `--server`. Other role commands, like `import`, seem to respect the server parameter properly.
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
ansible-galaxy
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
ansible 2.9.0b1
config file = /etc/ansible/ansible.cfg
configured module search path = ['/home/calvin/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /home/calvin/projects/ansible/lib/ansible
executable location = /home/calvin/.local/share/virtualenvs/orion/bin/ansible
python version = 3.6.9 (default, Jul 3 2019, 17:57:57) [GCC 8.3.1 20190223 (Red Hat 8.3.1-2)]
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
Fedora 29
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
<!--- Paste example playbooks or commands between quotes below -->
```yaml
ansible-galaxy -vvv install --server=http://galaxy-dev.ansible.com orionuser1.ansible_role_logstash
```
<!--- HINT: You can paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
Expect the given role to be installed from the specified Galaxy server, rather than the default production instance. Especially for automated tests which we do not want to run against production.
##### ACTUAL RESULTS
<!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) -->
<!--- Paste verbatim command output between quotes -->
```paste below
(orion) [calvin@localhost ansible]$ ansible-galaxy -vvv install --server=http://galaxy-dev.ansible.com orionuser1.ansible_role_logstash
[DEPRECATION WARNING]: Setting verbosity before the arg sub command is deprecated, set the verbosity after the sub command. This feature will be removed in version 2.13. Deprecation warnings can be disabled by
setting deprecation_warnings=False in ansible.cfg.
ansible-galaxy 2.9.0b1
config file = /etc/ansible/ansible.cfg
configured module search path = ['/home/calvin/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /home/calvin/projects/ansible/lib/ansible
executable location = /home/calvin/.local/share/virtualenvs/orion/bin/ansible-galaxy
python version = 3.6.9 (default, Jul 3 2019, 17:57:57) [GCC 8.3.1 20190223 (Red Hat 8.3.1-2)]
Using /etc/ansible/ansible.cfg as config file
Processing role orionuser1.ansible_role_logstash
- downloading role 'ansible_role_logstash', owned by orionuser1
[WARNING]: - orionuser1.ansible_role_logstash was NOT installed successfully: - sorry, orionuser1.ansible_role_logstash was not found on https://galaxy.ansible.com.
ERROR! - you can use --ignore-errors to skip failed roles and finish processing the list.
```
| https://github.com/ansible/ansible/issues/61609 | https://github.com/ansible/ansible/pull/61820 | f81b7dd10a674c72659b25be20461865bb997eed | 3a7b77a94ce534c502828ebd2959f6fdf9d183f5 | 2019-08-30T16:03:22Z | python | 2019-09-05T01:46:44Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,600 | ["lib/ansible/module_utils/network/iosxr/utils/utils.py", "test/integration/targets/iosxr_l3_interfaces/tests/cli/_populate_config.yaml", "test/integration/targets/iosxr_l3_interfaces/tests/cli/_remove_config.yaml", "test/integration/targets/iosxr_l3_interfaces/tests/cli/deleted.yaml", "test/integration/targets/iosxr_l3_interfaces/tests/cli/merged.yaml", "test/integration/targets/iosxr_l3_interfaces/tests/cli/overridden.yaml", "test/integration/targets/iosxr_l3_interfaces/tests/cli/replaced.yaml", "test/integration/targets/iosxr_l3_interfaces/vars/main.yaml"] | Override and Replace state not behaving ideally for Iosxr_l3_interfaces | <!--- Verify first that your issue is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
<!--- Explain the problem briefly below -->
For the Replace and Override use case, where `secondary ip` is already configured on to the device but in override and replace operation user tries to configure only IP without setting any secondary IP in that case already existing IP was not entirely replaced/overridden coz the new IP mentioned in play was set but the `secondary ip` was also coming as configured.
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
<!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure -->
iosxr_l3_interfaces
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
2.9
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
iosxr
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
```
```
##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
Without ISSUE `no ipv4 address` command fired for interface `GigabitEthernet0/0/0/1`
```
before:
- name: Loopback888
- name: Loopback999
- ipv4:
- address: 198.51.100.1 255.255.255.0
ipv6:
- address: 2001:db8::/32
name: GigabitEthernet0/0/0/0
- ipv4:
- address: 192.0.2.1 255.255.255.0
- address: 192.0.2.2 255.255.255.0
secondary: true
name: GigabitEthernet0/0/0/1
commands:
- "interface GigabitEthernet0/0/0/0"
- "no ipv4 address"
- "no ipv6 address"
- "interface GigabitEthernet0/0/0/1"
- "no ipv4 address"
- "ipv4 address 198.51.102.1 255.255.255.0"
- "ipv6 address 2001:db8:1::/64"
after:
- name: Loopback888
- name: Loopback999
- ipv4:
- address: 198.51.102.1 255.255.255.0
ipv6:
- address: 2001:db8:1::/64
name: GigabitEthernet0/0/0/1
```
##### ACTUAL RESULTS
<!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) -->
With Override, ISSUE
```
before:
- name: Loopback888
- name: Loopback999
- ipv4:
- address: 198.51.100.1 255.255.255.0
ipv6:
- address: 2001:db8::/32
name: GigabitEthernet0/0/0/0
- ipv4:
- address: 192.0.2.1 255.255.255.0
- address: 192.0.2.2 255.255.255.0
secondary: true
name: GigabitEthernet0/0/0/1
commands:
- "interface GigabitEthernet0/0/0/0"
- "no ipv4 address"
- "no ipv6 address"
- "interface GigabitEthernet0/0/0/1"
- "ipv4 address 198.51.102.1 255.255.255.0"
- "ipv6 address 2001:db8:1::/64"
after:
- name: Loopback888
- name: Loopback999
- ipv4:
- address: 198.51.102.1 255.255.255.0
- address: 192.0.2.2 255.255.255.0
secondary: true
ipv6:
- address: 2001:db8:1::/64
name: GigabitEthernet0/0/0/1
```
<!--- Paste verbatim command output between quotes -->
```paste below
```
| https://github.com/ansible/ansible/issues/61600 | https://github.com/ansible/ansible/pull/61592 | aaa8835311f39db42843efe19bd07c4691009eef | 24ad1dffc9ad18df7090cc3782fd87523449e955 | 2019-08-30T12:45:55Z | python | 2019-08-30T23:36:15Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,569 | ["changelogs/fragments/61805-azure-facts-info.yml", "lib/ansible/modules/cloud/azure/azure_rm_containerinstance_info.py", "lib/ansible/modules/cloud/azure/azure_rm_dnsrecordset_info.py", "lib/ansible/modules/cloud/azure/azure_rm_resourcegroup_info.py", "lib/ansible/modules/cloud/azure/azure_rm_sqlserver_info.py", "lib/ansible/modules/cloud/azure/azure_rm_storageaccount_info.py", "lib/ansible/modules/cloud/azure/azure_rm_virtualmachineimage_info.py", "lib/ansible/modules/cloud/azure/azure_rm_virtualmachinescaleset_info.py", "lib/ansible/modules/cloud/azure/azure_rm_virtualnetwork_info.py"] | Some azure _info modules still return ansible_facts when called as _info | ##### SUMMARY
Some of the modules still return something in `ansible_facts`, even though the result in there is an empty list:
- ~~`azure_rm_publicipaddress_info`~~
- ~~`azure_rm_networkinterface_info`~~
- `azure_rm_storageaccount_info`
- `azure_rm_virtualmachineimage_info`
- `azure_rm_virtualmachinescaleset_info`
- `azure_rm_virtualnetwork_info`
Finally, `azure_rm_resourcegroup_info` always returns `ansible_facts` with content (which is also returned as non-`ansible_facts`).
When called as `_info` modules, these modules should not have anything in `ansible_facts` when returning.
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
~~azure_rm_publicipaddress_info~~
~~azure_rm_networkinterface_info~~
azure_rm_resourcegroup_info
azure_rm_storageaccount_info
azure_rm_virtualmachineimage_info
azure_rm_virtualmachinescaleset_info
azure_rm_virtualnetwork_info
##### ANSIBLE VERSION
```paste below
2.9
```
| https://github.com/ansible/ansible/issues/61569 | https://github.com/ansible/ansible/pull/61805 | 2a932ad7cfe27663d47cbd43de124fc756632361 | e06dbe6e4f925b473acf0d03deda3b6d780a9dd3 | 2019-08-29T19:41:13Z | python | 2019-09-05T09:51:56Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,568 | ["changelogs/fragments/61570-netcli-put-get.yaml", "lib/ansible/plugins/action/net_get.py", "lib/ansible/plugins/action/net_put.py", "lib/ansible/plugins/cliconf/__init__.py", "lib/ansible/plugins/connection/network_cli.py", "test/units/plugins/connection/test_network_cli.py"] | net_put and possible other action plugins broken in devel | ##### SUMMARY
The `net_put` action plugin and likely other action plugins that use the `network_cli` connection plugin in the latest devel branch.
I tracked the problem to the following commit:
https://github.com/ansible/ansible/commit/7d3c4a88823846cbcea7c61de38658a6d63d4265
If I checkout the commit that immediately precedes this commit the module functions properly.
Note: This also impacts the following PR since I am using the same connection logic as `net_put`.
https://github.com/ansible/ansible/pull/60643
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
network_cli plugin
##### ANSIBLE VERSION
```paste below
ansible 2.9.0.dev0
config file = /etc/ansible/ansible.cfg
configured module search path = [u'/Users/mwiebe/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /Users/mwiebe/Projects/nxos_ansible/ansible_sanity_check/lib/ansible
executable location = /Users/mwiebe/Projects/nxos_ansible/ansible_sanity_check/bin/ansible
python version = 2.7.13 (default, Apr 4 2017, 08:47:57) [GCC 4.2.1 Compatible Apple LLVM 8.1.0 (clang-802.0.38)]
```
##### CONFIGURATION
```paste below
DEFAULT_ROLES_PATH(env: ANSIBLE_ROLES_PATH) = [u'/Users/mwiebe/Projects/nxos_ansible/ansible_sanity_check/test/integration/targets']
PARAMIKO_HOST_KEY_AUTO_ADD(env: ANSIBLE_PARAMIKO_HOST_KEY_AUTO_ADD) = True
PERSISTENT_COMMAND_TIMEOUT(env: ANSIBLE_PERSISTENT_COMMAND_TIMEOUT) = 1000
PERSISTENT_CONNECT_TIMEOUT(env: ANSIBLE_PERSISTENT_CONNECT_TIMEOUT) = 1000
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
##### STEPS TO REPRODUCE
I am using the following playbook to demonstrate the problem and running it against an Nexus n9k device.
```yaml
tasks:
- name: copy file from ansible controller to a network device
net_put:
src: '/Users/mwiebe/Projects/nxos_ansible/fix_ansible/test/integration/network-integration.cfg'
dest: 'bootflash:'
```
I added a debug tracepoint inside `net_put` to display the problem:
Checkout commit that immediately precedes the problem commit:
```git
commit 7d3c4a88823846cbcea7c61de38658a6d63d4265 (HEAD)
Author: Nathaniel Case <[email protected]>
Date: Wed Aug 14 16:58:03 2019 -0400
Delay persistent connection until needed (#59153)
* Delay calling connect() until absolutely necessary
* Implement transport_test to enable wait_for_connection
* plugin might be connected already for some reason?
* ensure_connect for httpapi
There's some become shenanigans still needing to be ironed out
* Fix tests for network_cli
commit f02f5c4b5dad36d696f028078ab545d75ba93d31
Author: René Moser <[email protected]>
Date: Wed Aug 14 22:55:31 2019 +0200
cloudscale_server: add tags support (#60396)
```
```
git checkout f02f5c4b5dad36d696f028078ab545d75ba93d31
```
Add tracepoint and run the test:
```diff
diff --git a/lib/ansible/plugins/action/net_put.py b/lib/ansible/plugins/action/net_put.py
index bf6dd52d29..6506b7d11b 100644
--- a/lib/ansible/plugins/action/net_put.py
+++ b/lib/ansible/plugins/action/net_put.py
@@ -98,6 +98,7 @@ class ActionModule(ActionBase):
socket_path = self._connection.socket_path
conn = Connection(socket_path)
+ import epdb ; epdb.set_trace()
sock_timeout = conn.get_option('persistent_command_timeout')
```
```diff
(Epdb) list
97 if socket_path is None:
98 socket_path = self._connection.socket_path
99
100 conn = Connection(socket_path)
101 import epdb ; epdb.set_trace()
102 -> sock_timeout = conn.get_option('persistent_command_timeout')
103
104 if dest is None:
105 dest = src_file_path_name
106
107 try:
(Epdb) conn.exec_command('show version')
u'Cisco Nexus Operating System (NX-OS) Software\nTAC support: http://www.cisco.com/tac\nCopyright (C) 2002-2019, Cisco and/or its affiliates.\nAll rights reserved.\nThe copyrights to certain works contained in this software are\nowned by other third parties and used and distributed under their own\nlicenses, such as open source. This software is provided "as is," and unless\notherwise stated, there is no warranty, express or implied, including but not\nlimited to warranties of merchantability and fitness for a particular purpose.\nCertain components of this software are licensed under\nthe GNU General Public License (GPL) version 2.0 or \nGNU General Public License (GPL) version 3.0 or the GNU\nLesser General Public License (LGPL) Version 2.1 or \nLesser General Public License (LGPL) Version 2.0. \nA copy of each such license is available at\nhttp://www.opensource.org/licenses/gpl-2.0.php and\nhttp://opensource.org/licenses/gpl-3.0.html and\nhttp://www.opensource.org/licenses/lgpl-2.1.php and\nhttp://www.gnu.org/licenses/old-licenses/library.txt.\n\nSoftware\n BIOS: version 08.34\n NXOS: version 9.3(1) [build 9.2(1)IDI9(0.334)]\n BIOS compile time: 04/26/2018\n NXOS image file is: bootflash:///nxos.glmatthe.bin\n NXOS compile time: 8/28/2019 17:00:00 [08/29/2019 18:32:39]\n\n\nHardware\n cisco Nexus9000 C9504 (4 Slot) Chassis ("Supervisor Module")\n Intel(R) Xeon(R) CPU E5-2403 0 @ 1.80GHz with 16399704 kB of memory.\n Processor Board ID SAL1909A7VC\n\n Device name: n9k-109\n bootflash: 53298520 kB\nKernel uptime is 0 day(s), 0 hour(s), 8 minute(s), 30 second(s)\n\nLast reset at 165683 usecs after Thu Aug 29 19:03:48 2019\n Reason: Reset Requested by CLI command reload\n System version: 9.3(1)\n Service: \n\nplugin\n Core Plugin, Ethernet Plugin\n\nActive Package(s):'
(Epdb)
```
As you can see it retrieves the version info properly.
Now, if I checkout 7d3c4a88823846cbcea7c61de38658a6d63d4265 I see the issue:
```
(Epdb) list
97 if socket_path is None:
98 socket_path = self._connection.socket_path
99
100 conn = Connection(socket_path)
101 import epdb ; epdb.set_trace()
102 -> sock_timeout = conn.get_option('persistent_command_timeout')
103
104 if dest is None:
105 dest = src_file_path_name
106
107 try:
(Epdb) conn.exec_command('show version')
[127, u'', u'/bin/sh: show: command not found\n']
(Epdb)
```
The exception behind this is:
```
"msg": "Exception received : 'NoneType' object has no attribute '_connect_uncached'"
``` | https://github.com/ansible/ansible/issues/61568 | https://github.com/ansible/ansible/pull/61570 | 6e8d430872820d2bcbcb010f092443403317a511 | 50e09be14f0b055440a3b7df7ed916c8c24bdae2 | 2019-08-29T19:15:51Z | python | 2019-09-09T20:59:20Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,553 | ["docs/docsite/rst/reference_appendices/galaxy.rst"] | Dead docs link to galaxy settings | ##### SUMMARY
https://github.com/ansible/ansible/blob/6ad40fd6b8b6319f9f3fff7bc6f854e951a82396/docs/docsite/rst/reference_appendices/galaxy.rst#L30-L31
in the text
> The command line tool by default communicates with the Galaxy website API using the server address https://galaxy.ansible.com. Since the Galaxy project is an open source project, you may be running your own internal Galaxy server and wish to override the default server address. You can do this using the --server option or by setting the Galaxy server value in your ansible.cfg file. For information on setting the value in ansible.cfg visit Galaxy Settings.
The word "Galaxy Settings" links to `/docs/docsite/rst/reference_appendices/intro_configuration.html#galaxy-settings`, which does not exist.
~Perhaps it should link to https://github.com/ansible/ansible/blob/6ad40fd6b8b6319f9f3fff7bc6f854e951a82396/docs/docsite/rst/reference_appendices/general_precedence.rst?~
I don't know where it should link to.
##### ISSUE TYPE
- Documentation Report
##### COMPONENT NAME
docs/docsite/rst/reference_appendices/galaxy.rst
##### ANSIBLE VERSION
current
##### CONFIGURATION
N/A
##### OS / ENVIRONMENT
N/A
##### ADDITIONAL INFORMATION
https://docs.ansible.com/ansible/latest/reference_appendices/galaxy.html
Ping @jborean93
| https://github.com/ansible/ansible/issues/61553 | https://github.com/ansible/ansible/pull/61823 | 173d47d1f429847ca351da92b69a0e05d25bb313 | 2fbe4ca102324661eb0c04de3f8fc7e96e472bbb | 2019-08-29T14:06:57Z | python | 2019-09-05T14:47:19Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,550 | ["test/lib/ansible_test/_internal/git.py", "test/lib/ansible_test/_internal/provider/source/git.py"] | ansible-test not finding roles in collections anymore | ##### SUMMARY
I have made no changes to my collection (geerlingguy.php_roles). Six days ago the CI tests passed without issue. Today I noticed the test structure changed (`test` directory is now `tests`), so I simply did a `mv test tests` and when the CI build ran, it picked up the tests as usual, but now I'm getting the following error about my collection role not being found:
```
TASK [Run the PHP role.] *******************************************************
584ERROR! the role 'geerlingguy.php_roles.php' was not found in /root/.ansible/test/tmp/php_role_test-zZQmcA-ÅÑŚÌβŁÈ/tests/integration/roles:/root/.ansible/test/tmp/php_role_test-zZQmcA-ÅÑŚÌβŁÈ/tests/integration/targets:/root/.ansible/test/tmp/php_role_test-zZQmcA-ÅÑŚÌβŁÈ/tests/integration
585
586The error appears to be in '/root/.ansible/test/tmp/php_role_test-zZQmcA-ÅÑŚÌβŁÈ/tests/integration/targets/php_role_test/tasks/main.yml': line 29, column 11, but may
587be elsewhere in the file depending on the exact syntax problem.
588
589The offending line appears to be:
590
591 include_role:
592 name: geerlingguy.php_roles.php
593 ^ here
```
I made no other changes besides moving the test directory to tests, so I'm wondering if core's logic for finding roles in the proper paths has a bug introduced in the past 6 days.
Last successful run: https://travis-ci.com/geerlingguy/ansible-collection-php_roles/builds/124407472
First failed run: https://travis-ci.com/geerlingguy/ansible-collection-php_roles/builds/125080018
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
ansible-test
##### ANSIBLE VERSION
```paste below
ansible 2.9.0.dev0
config file = /etc/ansible/ansible.cfg
configured module search path = [u'/Users/jgeerling/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /Users/jgeerling/Downloads/ansible/lib/ansible
executable location = /Users/jgeerling/Downloads/ansible/bin/ansible
python version = 2.7.16 (default, Apr 12 2019, 15:32:40) [GCC 4.2.1 Compatible Apple LLVM 10.0.1 (clang-1001.0.46.3)]
```
##### CONFIGURATION
```paste below
ANSIBLE_NOCOWS(/etc/ansible/ansible.cfg) = True
ANSIBLE_PIPELINING(/etc/ansible/ansible.cfg) = True
ANSIBLE_SSH_CONTROL_PATH(/etc/ansible/ansible.cfg) = /tmp/ansible-ssh-%%h-%%p-%%r
DEFAULT_FORKS(/etc/ansible/ansible.cfg) = 20
DEFAULT_HOST_LIST(/etc/ansible/ansible.cfg) = [u'/etc/ansible/hosts']
DEFAULT_ROLES_PATH(/etc/ansible/ansible.cfg) = [u'/Users/jgeerling/Dropbox/VMs/roles']
DEFAULT_STDOUT_CALLBACK(/etc/ansible/ansible.cfg) = yaml
RETRY_FILES_ENABLED(/etc/ansible/ansible.cfg) = False
```
##### OS / ENVIRONMENT
macOS (local), Ubuntu (Travis CI)
##### STEPS TO REPRODUCE
See summary above. Basically, run `ansible-test` within the collection's root directory. The collection is inside `~/.ansible/collections`
##### EXPECTED RESULTS
Tests should run without error as before.
##### ACTUAL RESULTS
Tests fail and the only paths scanned are:
- /root/.ansible/test/tmp/php_role_test-zZQmcA-ÅÑŚÌβŁÈ/tests/integration/roles
- /root/.ansible/test/tmp/php_role_test-zZQmcA-ÅÑŚÌβŁÈ/tests/integration/targets
- /root/.ansible/test/tmp/php_role_test-zZQmcA-ÅÑŚÌβŁÈ/tests/integration
It looks like it's not scanning the collections directory (where the test was run) at all. | https://github.com/ansible/ansible/issues/61550 | https://github.com/ansible/ansible/pull/61564 | 3881326ae28131d4c8a3f629299d60517333c929 | 2215a62057b5278824663639aa539742d993aa8b | 2019-08-29T13:30:38Z | python | 2019-08-29T19:21:28Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,549 | ["lib/ansible/module_utils/network/checkpoint/checkpoint.py"] | replace inner params to contain '-' instead of '_' and get relevant error for the user | <!--- Verify first that your issue is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
<!--- Explain the problem briefly below -->
replace inner params to contain '-' instead of '_' and get relevant error for the user
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
<!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure -->
checkpoint
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
<!--- Paste example playbooks or commands between quotes below -->
```yaml
```
<!--- HINT: You can paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
##### ACTUAL RESULTS
<!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) -->
<!--- Paste verbatim command output between quotes -->
```paste below
```
| https://github.com/ansible/ansible/issues/61549 | https://github.com/ansible/ansible/pull/61542 | 41e4ece44bf82ebbb4204b42688aba08b15eeee5 | a321e58c73b0cbbc45f94933b96a070e17963587 | 2019-08-29T13:23:24Z | python | 2019-08-29T13:30:51Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,547 | ["lib/ansible/modules/network/eos/eos_logging.py", "lib/ansible/modules/network/ios/ios_logging.py"] | _net_logging and ios_logging dest: file | <!--- Verify first that your improvement is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
<!--- Explain the problem briefly below, add suggestions to wording or structure -->
In net_logging documentation examples, 'file' is used as 'dest:' but not mentioned in parameters choices
In ios_logging, the parameter 'name' says "If value of dest is file it indicates file-name" but again 'file' is not stated as a valid 'dest' choice.
I can update the doc for net_logging as it seems file is a valid choice because it is used in examples but for ios_logging, I'm not sure if it's a typo or if 'file' should be valid too.
<!--- HINT: Did you know the documentation has an "Edit on GitHub" link on every page ? -->
##### ISSUE TYPE
- Documentation Report
##### COMPONENT NAME
<!--- Write the short name of the rst file, module, plugin, task or feature below, use your best guess if unsure -->
net_logging, ios_logging
##### ADDITIONAL INFORMATION
<!--- Describe how this improves the documentation, e.g. before/after situation or screenshots -->
<!--- HINT: You can paste gist.github.com links for larger files -->
| https://github.com/ansible/ansible/issues/61547 | https://github.com/ansible/ansible/pull/61777 | f406b8b4c4046f31330347e4456147cb85e44a27 | cc9adf7f1ae819db13c77ee99da824be8b762ec5 | 2019-08-29T13:14:31Z | python | 2019-09-05T12:58:57Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,535 | ["lib/ansible/modules/network/ios/ios_facts.py"] | ios_facts 2.9 - gather_subset min | <!--- Verify first that your improvement is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
<!--- Explain the problem briefly below, add suggestions to wording or structure -->
Following merge of #59716 revamping ios_facts module, the doc states the 'min' subset in examples but it's not defined in 'Documentation' supported options.
And in module_utils/network/ios/facts/facts.py ; the dict FACT_LEGACY_SUBSETS doesn't mention this 'min' subset.
<!--- HINT: Did you know the documentation has an "Edit on GitHub" link on every page ? -->
##### ISSUE TYPE
- Documentation Report
##### COMPONENT NAME
<!--- Write the short name of the rst file, module, plugin, task or feature below, use your best guess if unsure -->
ios_facts module
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
2.9
```
##### ADDITIONAL INFORMATION
<!--- Describe how this improves the documentation, e.g. before/after situation or screenshots -->
<!--- HINT: You can paste gist.github.com links for larger files -->
| https://github.com/ansible/ansible/issues/61535 | https://github.com/ansible/ansible/pull/61536 | 017562013ad4e7d0cd38f9fb40276d860788c91e | cee54d55d0766afe100f08ba4063d3bf14761d7b | 2019-08-29T11:32:15Z | python | 2019-08-29T13:58:20Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,513 | ["docs/docsite/rst/inventory/implicit_localhost.rst"] | hostvars not set with implicit localhost | ##### SUMMARY
The following
```yaml
- hosts: localhost
connection: local
tasks:
- debug:
msg: '{{ hostvars.values() | first }}'
```
If I run it with an explicitly empty inventory like
```yaml
all:
hosts: {}
```
I get the following (where I see the warning about implicit localhost)
```
$ ./ansible-env/bin/ansible-playbook -i inventory.yaml ./test.yaml
[WARNING]: provided hosts list is empty, only localhost is available. Note that
the implicit localhost does not match 'all'
PLAY [localhost] *******************************************************************
TASK [Gathering Facts] *************************************************************
ok: [localhost]
TASK [debug] ***********************************************************************
fatal: [localhost]: FAILED! => {"msg": "The task includes an option with an undefined variable. The error was: No first item, sequence was empty.\n\nThe error appears to be in '/home/iwienand/tmp/test.yaml': line 5, column 7, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n - debug:\n ^ here\n"}
```
However, if I change the inventory to
```yaml
all:
hosts:
localhost:
vars:
ansible_connection: local
```
(or, indeed run it via ```$ ./ansible-env/bin/ansible-playbook -i 'localhost,' ./test.yaml```) then accessing ```hostvars``` works OK.
Ergo, it seems that ```hostvars``` isn't defined when using the implicit ```localhost```? I did not see that explicitly mentioned in https://docs.ansible.com/ansible/latest/inventory/implicit_localhost.html but perhaps that is what "not targetable via any group" means?
I'd be happy for advice if this is unexpected behaviour, or perhaps I could clarify the documentation further.
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
##### ANSIBLE VERSION
```
ansible 2.8.4
config file = None
configured module search path = ['/home/iwienand/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /home/iwienand/tmp/ansible-env/lib/python3.7/site-packages/ansible
executable location = ./ansible-env/bin/ansible
python version = 3.7.4 (default, Jul 9 2019, 16:32:37) [GCC 9.1.1 20190503 (Red Hat 9.1.1-1)]
```
| https://github.com/ansible/ansible/issues/61513 | https://github.com/ansible/ansible/pull/61956 | 7a36606574168777e1e41708cdc257ef6ad18569 | b1afb37ac92645c7a2017047fa21f4ce1e2020d8 | 2019-08-29T06:05:47Z | python | 2019-09-16T18:00:29Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,497 | ["changelogs/fragments/parsing-splitter-fixes.yml", "lib/ansible/parsing/splitter.py", "test/units/parsing/test_splitter.py"] | placing empty --extra-vars results in error | <!--- Verify first that your issue is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
I don't even know if this is worth fixing, but it did cause me an issue.
`--extra-vars ' '` now throws an error when it never used to. I'm essentially doing this in a script...
`--extra-vars "$extra_vars $vmware_restore"` which results in a space when both are empty.
`--extra-vars ''` with no space, works fine.
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
ansible playbook
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
$ ansible --version
ansible 2.8.4
config file = /home/trenta/Documents/development/java/cas/cas-overlay-template/ansible/ansible.cfg
configured module search path = [u'/home/trenta/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python2.7/dist-packages/ansible
executable location = /usr/bin/ansible
python version = 2.7.12 (default, Nov 12 2018, 14:36:49) [GCC 5.4.0 20160609]
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
$ ansible-config dump --only-changed
ANSIBLE_NOCOWS(env: ANSIBLE_NOCOWS) = True
ANSIBLE_PIPELINING(/home/trenta/Documents/development/java/cas/cas-overlay-template/ansible/ansible.cfg) = True
ANSIBLE_SSH_ARGS(/home/trenta/Documents/development/java/cas/cas-overlay-template/ansible/ansible.cfg) = -o ControlMaster=auto -o ControlPersist=60s
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
Likely not relevant, but I'm using Linux Mint 18.2.
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
<!--- Paste example playbooks or commands between quotes below -->
```bash
# note the space in --extra-vars
ansible-playbook -i inventory --extra-vars ' ' -v site.yml --diff
```
<!--- HINT: You can paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
I expected the playbook to run, as it always has on previous versions of ansible.
##### ACTUAL RESULTS
<!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) -->
<!--- Paste verbatim command output between quotes -->
```paste below
ansible-playbook 2.8.4
config file = /home/trenta/Documents/development/java/cas/cas-overlay-template/ansible/ansible.cfg
configured module search path = [u'/home/trenta/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python2.7/dist-packages/ansible
executable location = /usr/bin/ansible-playbook
python version = 2.7.12 (default, Nov 12 2018, 14:36:49) [GCC 5.4.0 20160609]
Using /home/trenta/Documents/development/java/cas/cas-overlay-template/ansible/ansible.cfg as config file
vault.sh: myname: vault.sh
vault.sh: fullname: /home/trenta/Documents/development/java/cas/cas-overlay-template/ansible/vault.sh
vault.sh: dirname: /home/trenta/Documents/development/java/cas/cas-overlay-template/ansible
vault.sh: project: cas-5.2
vault.sh: file: ansible-vault/dev-cas-5.2
vault.sh: password: host_list declined parsing /home/trenta/Documents/development/java/cas/cas-overlay-template/ansible/inventory as it did not pass it's verify_file() method
script declined parsing /home/trenta/Documents/development/java/cas/cas-overlay-template/ansible/inventory as it did not pass it's verify_file() method
auto declined parsing /home/trenta/Documents/development/java/cas/cas-overlay-template/ansible/inventory as it did not pass it's verify_file() method
Parsed /home/trenta/Documents/development/java/cas/cas-overlay-template/ansible/inventory inventory source with ini plugin
ERROR! Unexpected Exception, this is probably a bug: list index out of range
the full traceback was:
Traceback (most recent call last):
File "/usr/bin/ansible-playbook", line 110, in <module>
exit_code = cli.run()
File "/usr/lib/python2.7/dist-packages/ansible/cli/playbook.py", line 104, in run
loader, inventory, variable_manager = self._play_prereqs()
File "/usr/lib/python2.7/dist-packages/ansible/cli/__init__.py", line 492, in _play_prereqs
variable_manager = VariableManager(loader=loader, inventory=inventory, version_info=CLI.version_info(gitinfo=False))
File "/usr/lib/python2.7/dist-packages/ansible/vars/manager.py", line 98, in __init__
self._extra_vars = load_extra_vars(loader=self._loader)
File "/usr/lib/python2.7/dist-packages/ansible/utils/vars.py", line 136, in load_extra_vars
data = parse_kv(extra_vars_opt)
File "/usr/lib/python2.7/dist-packages/ansible/parsing/splitter.py", line 62, in parse_kv
vargs = split_args(args)
File "/usr/lib/python2.7/dist-packages/ansible/parsing/splitter.py", line 206, in split_args
params[-1] += ' '
```
| https://github.com/ansible/ansible/issues/61497 | https://github.com/ansible/ansible/pull/80030 | 98d1cf7aa2519dd1c33cb3f3d94082e832f840c4 | da2cd157f151ad1244296df54603698075faf5d2 | 2019-08-28T22:50:26Z | python | 2023-06-22T23:19:52Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,459 | ["docs/docsite/_static/ansible.css"] | Refine CSS for docsite, prepare for future theme upgrades | ##### SUMMARY
Follow-up to #61189 and #58832.
Make sure all Ansible-specific CSS is separated from the underlying Sphinx theme. Then re-minify the CSS for the docsite.
##### ISSUE TYPE
- Documentation Report
##### COMPONENT NAME
docs.ansible.comb
##### ANSIBLE VERSION
2.9
##### CONFIGURATION
N/A
##### OS / ENVIRONMENT
N/A
| https://github.com/ansible/ansible/issues/61459 | https://github.com/ansible/ansible/pull/61792 | 736938625bdd686739b7326f054b29adafefd71a | 7efaad711e769f1f4ea04e763d7c5796324e1db9 | 2019-08-28T15:50:30Z | python | 2019-09-04T17:57:05Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,421 | ["changelogs/fragments/58824-vmware_cluster_ha-advanced-settings.yml", "lib/ansible/module_utils/vmware.py", "lib/ansible/modules/cloud/vmware/vmware_cluster_ha.py", "test/integration/targets/vmware_cluster_ha/tasks/main.yml"] | vmware_cluster_ha support for advanced configuration parameters | <!--- Verify first that your feature was not already discussed on GitHub -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
The vmware_cluster_ha module should support advanced configuration parameters in a generic way.
##### ISSUE TYPE
- Feature Idea
##### COMPONENT NAME
vmware_cluster_ha
##### ADDITIONAL INFORMATION
The feature would allow advanced configurations like isolation address handling.
<!--- Paste example playbooks or commands between quotes below -->
```yaml
name: Enable HA with multiple custom isolation addresses for stretched vSAN
vmware_cluster_ha:
hostname: '{{ vcenter_hostname }}'
username: '{{ vcenter_username }}'
password: '{{ vcenter_password }}'
datacenter_name: datacenter
cluster_name: cluster
enable_ha: yes
configuration_parameters:
das.usedefaultisolationaddress: false
das.isolationaddress0: '{{ primary_isolation_address }}'
das.isolationaddress1: '{{ secondary_isolation_address }}'
delegate_to: localhost
```
<!--- HINT: You can also paste gist.github.com links for larger files -->
| https://github.com/ansible/ansible/issues/61421 | https://github.com/ansible/ansible/pull/65675 | c8704573396e7480b3e1b33b2ddda2b6325d0d80 | fec883dfffcd8685d5d57a07463e402c2cd36931 | 2019-08-28T08:26:05Z | python | 2019-12-19T19:19:45Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,411 | ["changelogs/fragments/61658-openssh_keypair-public-key-permissions.yml", "lib/ansible/modules/crypto/openssh_keypair.py"] | openssh_keygen does not set permissions correctly on public key | <!--- Verify first that your issue is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
In the openssh_keypair module, `set_fs_attributes_if_different` is not called on the public key, so the owner and group do not get set on the .pub file containing the public key.
I haven't tested it or reasoned about the code, but this may only occur when trying to run the task when the public key already exists.
<https://github.com/ansible/ansible/blob/devel/lib/ansible/modules/crypto/openssh_keypair.py#L231>
In this line, file_args only receives the private key file location.
Additionally, there are "isPublicKeyValid" and "isPrivateKeyValid", and in the private key one we can see here <https://github.com/ansible/ansible/blob/devel/lib/ansible/modules/crypto/openssh_keypair.py#L254> that we check the permissions for the private key, but there is no corresponding check in the public key.
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
<!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure -->
openssh_keypair
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
ansible 2.8.4
config file = <path_inside_home_directory>/ansible.cfg
configured module search path = ['<home_directory>/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python3.7/site-packages/ansible
executable location = /usr/bin/ansible
python version = 3.7.4 (default, Jul 16 2019, 07:12:58) [GCC 9.1.0]
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
DEFAULT_HOST_LIST(<path_inside_home_directory>/aws-remote-work/ansible.cfg) = ['<path_inside_home_directory>/aws-remote-work/hosts']
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
host: Linux host-machine 5.2.9-arch1-1-ARCH #1 SMP PREEMPT Fri Aug 16 11:29:43 UTC 2019 x86_64 GNU/Linux
remote: Linux remote-machine 4.9.0-9-amd64 #1 SMP Debian 4.9.168-1+deb9u5 (2019-08-11) x86_64 GNU/Linux
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
I am running the playbook with --become, so that it's executing as root
<!--- Paste example playbooks or commands between quotes below -->
```yaml
- name: create ssh keypair in user home directory
openssh_keypair:
path: "/home/{{user_name}}/.ssh/my_ssh_key"
type: ecdsa
owner: "{{user_name}}"
group: "users"
mode: "u=rw,g=,o="
```
##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
my_ssh_key should have permissions like
`-rw------- 1 user_name users`
my_ssh_key.pub should have the same permissions:
`-rw------- 1 user_name users`
##### ACTUAL RESULTS
<!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) -->
only the private key has the correct permissions, and the public key has permissions
`-rw-r--r-- 1 root root`
| https://github.com/ansible/ansible/issues/61411 | https://github.com/ansible/ansible/pull/61658 | c77ab110514900ee439c7281a1d1dd14504cf44a | c19cea9b03f343a6c7da6607ce355ffa409e985a | 2019-08-27T20:27:05Z | python | 2019-09-10T04:44:04Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,396 | ["lib/ansible/module_utils/network/ios/utils/utils.py"] | ios_l3_interfaces can't do round trip (gather_facts->data model->push back to device) b/c of cidr / notation | ##### SUMMARY
when you gather_facts for ios_l3_interfaces
it will gather the full subnet (e.g. 255.255.255.0 instead of /24)
```
l3_interfaces:
- ipv4:
- address: 192.168.1.101 255.255.255.0
name: loopback0
- ipv4:
- address: 10.1.1.101 255.255.255.0
name: loopback1
```
but if you push this acquired data model back out, it will do this->
```
msg: address format is <ipv4 address>/<mask>, got invalid format 10.10.10.1 255.255.255.0
```
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
ios_l3_interfaces
##### ANSIBLE VERSION
```paste below
ansible 2.9.0.dev0
config file = /home/student1/.ansible.cfg
configured module search path = [u'/home/student1/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /home/student1/.local/lib/python2.7/site-packages/ansible
executable location = /usr/bin/ansible
python version = 2.7.5 (default, Jun 11 2019, 14:33:56) [GCC 4.8.5 20150623 (Red Hat 4.8.5-39)]
```
##### CONFIGURATION
```paste below
DEFAULT_HOST_LIST(/home/student1/.ansible.cfg) = [u'/home/student1/networking-workshop/lab_inventory/hosts']
DEFAULT_STDOUT_CALLBACK(/home/student1/.ansible.cfg) = yaml
DEFAULT_TIMEOUT(/home/student1/.ansible.cfg) = 60
DEPRECATION_WARNINGS(/home/student1/.ansible.cfg) = False
HOST_KEY_CHECKING(/home/student1/.ansible.cfg) = False
PERSISTENT_COMMAND_TIMEOUT(/home/student1/.ansible.cfg) = 60
PERSISTENT_CONNECT_TIMEOUT(/home/student1/.ansible.cfg) = 60
RETRY_FILES_ENABLED(/home/student1/.ansible.cfg) = False
```
##### OS / ENVIRONMENT
```
NAME="Red Hat Enterprise Linux Server"
VERSION="7.6 (Maipo)"
ID="rhel"
ID_LIKE="fedora"
VARIANT="Server"
VARIANT_ID="server"
VERSION_ID="7.6"
PRETTY_NAME="Red Hat Enterprise Linux Server 7.6 (Maipo)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:7.6:GA:server"
HOME_URL="https://www.redhat.com/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 7"
REDHAT_BUGZILLA_PRODUCT_VERSION=7.6
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="7.6"
Red Hat Enterprise Linux Server release 7.6 (Maipo)
Red Hat Enterprise Linux Server release 7.6 (Maipo)
```
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
<!--- Paste example playbooks or commands between quotes below -->
```yaml
---
- hosts: rtr1
gather_facts: false
tasks:
- name: grab info
ios_facts:
gather_subset: min
gather_network_resources: l3_interfaces
register: facts_for_sean
- name: print interface_info
debug:
msg: "{{ansible_network_resources}}"
- name: print facts
debug:
var: facts_for_sean
```
which results in
```
l3_interfaces:
- ipv4:
- address: 192.168.1.101 255.255.255.0
name: loopback0
- ipv4:
- address: 10.1.1.101 255.255.255.0
name: loopback1
- ipv4:
- address: 10.10.10.1 255.255.255.0
ipv6:
- address: fc00::100/64
- address: fc00::101/64
name: loopback100
- ipv4:
- address: dhcp
name: GigabitEthernet1
```
now try to merge those->
```
- ios_l3_interfaces:
config: "{{config}}"
state: merged
```
you will get something like
```
TASK [ios_l3_interfaces] ***********************************************************************************************
fatal: [rtr1]: FAILED! => changed=false
msg: address format is <ipv4 address>/<mask>, got invalid format 10.10.10.1 255.255.255.0
```
##### EXPECTED RESULTS
OK pass
##### ACTUAL RESULTS
failed, does not work, wants `/24` notation
| https://github.com/ansible/ansible/issues/61396 | https://github.com/ansible/ansible/pull/61642 | 037401b6e0d5c500774e2a259909e6fa7e3f16e2 | f9fd1f3626170a4370335648bba056a8d4913242 | 2019-08-27T16:48:01Z | python | 2019-09-17T08:10:32Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,382 | ["changelogs/fragments/64810-hostname-add-manjaro-linux-distribution.yml", "lib/ansible/modules/system/hostname.py"] | Hostname module doesn't work on a Manjaro Linux host | ##### SUMMARY
The hostname module reports that it doesn't work on Manjaro Linux, eventhough this is simply an Arch based distribution. So I think it should work without any modification if Manjaro is 'whitelisted' as a platform that supports this module.
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
Hostname module.
##### ANSIBLE VERSION
```ansible 2.8.3
config file = /home/overlord/ConfigManagement/ansible/ansible.cfg
configured module search path = ['/home/overlord/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python3.7/site-packages/ansible
executable location = /usr/bin/ansible
python version = 3.7.4 (default, Jul 16 2019, 07:12:58) [GCC 9.1.0]
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```
ANSIBLE_NOCOWS = True
ANSIBLE_PIPELINING = True
ANSIBLE_SSH_ARGS = -C -o ControlMaster=auto -o ControlPersist=300s -o ServerAliveInterval=2
ANSIBLE_SSH_CONTROL_PATH = %(directory)s/%%h-%%r
ANSIBLE_SSH_CONTROL_PATH_DIR = /tmp/ansible-cp
COMMAND_WARNINGS = False
DEFAULT_ASK_PASS = True
DEFAULT_BECOME_ASK_PASS = True
DEFAULT_FORKS = 50
DEFAULT_GATHERING = smart
DEFAULT_HOST_LIST = ['/home/overlord/ConfigManagement/ansible/inventory']
DEFAULT_INTERNAL_POLL_INTERVAL = 0.005
DEFAULT_LOCAL_TMP = /tmp/ansible-local/ansible-local-13795g9m3yhv0
DEFAULT_MANAGED_STR = This file is managed by Ansible.%n
template: {file}
user: {uid}
host: {host}
DO NOT EDIT BY HAND!!!!
DEFAULT_POLL_INTERVAL = 15
DEFAULT_ROLES_PATH = ['/home/myuser/ConfigManagement/ansible/roles', '/home/myuser/ConfigManagement/ansible/galaxyroles', '/home/myuser/ConfigManagement/ansible/software']
DEFAULT_SSH_TRANSFER_METHOD = piped
DEFAULT_TIMEOUT = 30
DISPLAY_SKIPPED_HOSTS = False
HOST_KEY_CHECKING = False
RETRY_FILES_ENABLED = False
```
##### OS / ENVIRONMENT
Ansible host is Manjaro Linux (current version, all packages up-to-date) and the target host is localhost (in this case).
##### STEPS TO REPRODUCE
My task is:
```
- name: "Zorgen dat de hostname {{ baseline_hostname }} is"
hostname:
name: "{{ baseline_hostname }}"
```
This code works fine on Ubuntu based hosts on the same network, using the same role which includes this task.
##### EXPECTED RESULTS
It should work fine if a Manjaro host is seen by Ansible as an Arch Linux host.
##### ACTUAL RESULTS
```
fatal: [myhost.mydomain.local]: FAILED! => {"changed": false, "msg": "hostname module cannot be used on platform Linux (Manjaro)"}
```
| https://github.com/ansible/ansible/issues/61382 | https://github.com/ansible/ansible/pull/64810 | e0373a73a87fb5a22b38316f25af3d1c5628ec9f | a75a79b84c9f41321b5bfdf57000f0922fc11715 | 2019-08-27T15:03:07Z | python | 2019-11-14T09:01:21Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,369 | ["changelogs/fragments/61369_get_url.yml", "lib/ansible/modules/get_url.py", "test/integration/targets/get_url/tasks/main.yml"] | get_url: check mode not supported when using checksum URL | ##### SUMMARY
<!--- Explain the problem briefly below -->
get_url does not support check mode (`--check`) when using the checksum format `<algorithm>:<url>`.
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
- get_url
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
ansible 2.8.4
config file = /etc/ansible/ansible.cfg
configured module search path = [u'/home/nbe/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /home/nbe/.local/lib/python2.7/site-packages/ansible
executable location = /home/nbe/.local/bin/ansible
python version = 2.7.15+ (default, Nov 27 2018, 23:36:35) [GCC 7.3.0]
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
- Ubuntu 18.04.3 LTS
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
Run playbook in check mode: `ansible-playbook --check site.yml`
<!--- Paste example playbooks or commands between quotes below -->
```yaml
---
- hosts: localhost
connection: local
vars:
vault_version: '1.2.2'
tasks:
- name: Download zip archive using checksum
get_url:
url: 'https://releases.hashicorp.com/vault/{{ vault_version }}/vault_{{ vault_version }}_linux_amd64.zip'
dest: '/tmp/vault_{{ vault_version }}_linux_amd64.zip'
checksum: 'sha256:7725b35d9ca8be3668abe63481f0731ca4730509419b4eb29fa0b0baa4798458'
- name: Download zip archive using checksum url
get_url:
url: 'https://releases.hashicorp.com/vault/{{ vault_version }}/vault_{{ vault_version }}_linux_amd64.zip'
dest: '/tmp/vault_{{ vault_version }}_linux_amd64_2.zip'
checksum: 'sha256:https://releases.hashicorp.com/vault/{{ vault_version }}/vault_{{ vault_version }}_SHA256SUMS'
```
<!--- HINT: You can paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
The second task `'Download zip archive using checksum url'` using the format `<algorithm>:<url>` must not fail and should show the same result as the first task (ok/changed) in check mode.
##### ACTUAL RESULTS
<!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) -->
The second task `'Download zip archive using checksum url'` using the format `<algorithm>:<url>` fails in check mode:
<!--- Paste verbatim command output between quotes -->
```paste below
fatal: [localhost]: FAILED! => {
"changed": false,
"invocation": {
"module_args": {
"attributes": null,
"backup": null,
"checksum": "sha256:https://releases.hashicorp.com/vault/1.2.2/vault_1.2.2_SHA256SUMS",
"client_cert": null,
"client_key": null,
"content": null,
"delimiter": null,
"dest": "/tmp/vault_1.2.2_linux_amd64.zip",
"directory_mode": null,
"follow": false,
"force": false,
"force_basic_auth": false,
"group": null,
"headers": null,
"http_agent": "ansible-httpget",
"mode": null,
"owner": null,
"regexp": null,
"remote_src": null,
"selevel": null,
"serole": null,
"setype": null,
"seuser": null,
"sha256sum": "",
"src": null,
"timeout": 10,
"tmp_dest": null,
"unsafe_writes": null,
"url": "https://releases.hashicorp.com/vault/1.2.2/vault_1.2.2_linux_amd64.zip",
"url_password": null,
"url_username": null,
"use_proxy": true,
"validate_certs": true
}
},
"msg": "Unable to find a checksum for file 'vault_1.2.2_linux_amd64.zip' in 'https://releases.hashicorp.com/vault/1.2.2/vault_1.2.2_SHA256SUMS'"
}
```
| https://github.com/ansible/ansible/issues/61369 | https://github.com/ansible/ansible/pull/66700 | aa56a2ff6a56697342908cc0cc85a537ecea4325 | 42bc03f0f5740f2340fcdbe75557920552622ac3 | 2019-08-27T12:32:44Z | python | 2020-12-22T16:04:42Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,354 | ["test/lib/ansible_test/_internal/executor.py", "test/lib/ansible_test/_internal/integration/__init__.py", "test/lib/ansible_test/_internal/provider/layout/__init__.py", "test/lib/ansible_test/_internal/provider/layout/ansible.py", "test/lib/ansible_test/_internal/provider/layout/collection.py", "test/lib/ansible_test/_internal/sanity/__init__.py", "test/lib/ansible_test/_internal/target.py", "test/lib/ansible_test/_internal/units/__init__.py", "test/lib/ansible_test/_internal/util_common.py"] | Support collection roles as integration test targets | ##### SUMMARY
Support collection roles as integration test targets.
Now that https://github.com/ansible/ansible/issues/59462 has been merged, ansible-test can be updated to support running integration test targets that are collection roles.
The planned convention is to look for targets under `roles/test/` and allow use of target-specific plugins from `plugins/{plugin_type}/test/{target_name}/`.
##### ISSUE TYPE
Feature Idea
##### COMPONENT NAME
ansible-test
##### ADDITIONAL INFORMATION
This will allow integration test targets to be written using collections instead of pre-collection roles. | https://github.com/ansible/ansible/issues/61354 | https://github.com/ansible/ansible/pull/61523 | 0922407b67790760a423e61f6eb98618afaec1e4 | f90587069cef9d96fe24265866c59c0e841008d5 | 2019-08-27T00:18:40Z | python | 2019-08-29T10:39:03Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,332 | ["changelogs/fragments/vmware_host_firewall_manager_fix_61332.yaml", "lib/ansible/modules/cloud/vmware/vmware_host_firewall_manager.py", "test/integration/targets/prepare_vmware_tests/tasks/teardown.yml", "test/integration/targets/vmware_host_firewall_manager/tasks/main.yml"] | vmware_host_firewall_manager: TypeError: 'NoneType' object is not subscriptable | ##### SUMMARY
The function test of `vmware_host_firewall_manager` is currently broken. This seems to be a regression introduced with https://github.com/ansible/ansible/pull/56733.
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
vmware_host_firewall_manager
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
devel
```
##### STEPS TO REPRODUCE
The first step of the functional test:
https://github.com/ansible/ansible/blob/devel/test/integration/targets/vmware_host_firewall_manager/tasks/main.yml
```yaml
- name: Disable the Firewall vvold rule on the ESXi
vmware_host_firewall_manager:
hostname: '{{ vcenter_hostname }}'
username: '{{ vcenter_username }}'
password: '{{ vcenter_password }}'
cluster_name: '{{ ccr1 }}'
validate_certs: no
rules:
- name: vvold
enabled: False
```
##### ACTUAL RESULTS
```paste below
TASK [vmware_host_firewall_manager : Disable the Firewall vvold rule on the ESXi] ****************************************************************
task path: /home/goneri/.ansible/test/tmp/vmware_host_firewall_manager-mn0bxgye-ÅÑŚÌβŁÈ/test/integration/targets/vmware_host_firewall_manager/tasks/main.yml:11
<testhost> ESTABLISH LOCAL CONNECTION FOR USER: goneri
<testhost> EXEC /bin/sh -c 'echo ~goneri && sleep 0'
<testhost> EXEC /bin/sh -c '( umask 77 && mkdir -p "` echo /home/goneri/.ansible/tmp/ansible-tmp-1566836629.9222088-161847597588297 `" && echo ansible-tmp-1566836629.9222088-161847597588297="` echo /home/goneri/.ansible/tmp/ansible-tmp-1566836629.9222088-161847597588297 `" ) && sleep 0'
Using module file /home/goneri/git_repos/ansible_projects/b/lib/ansible/modules/cloud/vmware/vmware_host_firewall_manager.py
<testhost> PUT /home/goneri/.ansible/tmp/ansible-local-25543igy5eduv/tmp1tecxld1 TO /home/goneri/.ansible/tmp/ansible-tmp-1566836629.9222088-161847597588297/AnsiballZ_vmware_host_firewall_manager.py
<testhost> EXEC /bin/sh -c 'chmod u+x /home/goneri/.ansible/tmp/ansible-tmp-1566836629.9222088-161847597588297/ /home/goneri/.ansible/tmp/ansible-tmp-1566836629.9222088-161847597588297/AnsiballZ_vmware_host_firewall_manager.py && sleep 0'
<testhost> EXEC /bin/sh -c 'ESXI1_HOSTNAME=esxi1.test ESXI1_PASSWORD='"'"'!234AaAa56'"'"' ESXI1_USERNAME=root ESXI2_HOSTNAME=esxi2.test ESXI2_PASSWORD='"'"'!234AaAa56'"'"' ESXI2_USERNAME=root VCENTER_HOSTNAME=vcenter.test VCENTER_PASSWORD='"'"'!234AaAa56'"'"' [email protected] VMWARE_VALIDATE_CERTS=no /home/goneri/git_repos/ansible_projects/b/.virtualenv/py37/bin/python /home/goneri/.ansible/tmp/ansible-tmp-1566836629.9222088-161847597588297/AnsiballZ_vmware_host_firewall_manager.py && sleep 0'
<testhost> EXEC /bin/sh -c 'rm -f -r /home/goneri/.ansible/tmp/ansible-tmp-1566836629.9222088-161847597588297/ > /dev/null 2>&1 && sleep 0'
The full traceback is:
Traceback (most recent call last):
File "/home/goneri/.ansible/tmp/ansible-tmp-1566836629.9222088-161847597588297/AnsiballZ_vmware_host_firewall_manager.py", line 139, in <module>
_ansiballz_main()
File "/home/goneri/.ansible/tmp/ansible-tmp-1566836629.9222088-161847597588297/AnsiballZ_vmware_host_firewall_manager.py", line 131, in _ansiballz_main
invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS)
File "/home/goneri/.ansible/tmp/ansible-tmp-1566836629.9222088-161847597588297/AnsiballZ_vmware_host_firewall_manager.py", line 65, in invoke_module
spec.loader.exec_module(module)
File "<frozen importlib._bootstrap_external>", line 728, in exec_module
File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
File "/tmp/ansible_vmware_host_firewall_manager_payload_kf53ugy0/__main__.py", line 367, in <module>
File "/tmp/ansible_vmware_host_firewall_manager_payload_kf53ugy0/__main__.py", line 363, in main
File "/tmp/ansible_vmware_host_firewall_manager_payload_kf53ugy0/__main__.py", line 238, in ensure
TypeError: 'NoneType' object is not subscriptable
fatal: [testhost]: FAILED! => {
"changed": false,
"module_stderr": "Traceback (most recent call last):\n File \"/home/goneri/.ansible/tmp/ansible-tmp-1566836629.9222088-161847597588297/AnsiballZ_vmware_host_firewall_manager.py\", line 139, in <module>\n _ansiballz_main()\n File \"/home/goneri/.ansible/tmp/ansible-tmp-1566836629.9222088-161847597588297/AnsiballZ_vmware_host_firewall_manager.py\", line 131, in _ansiballz_main\n invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS)\n File \"/home/goneri/.ansible/tmp/ansible-tmp-1566836629.9222088-161847597588297/AnsiballZ_vmware_host_firewall_manager.py\", line 65, in invoke_module\n spec.loader.exec_module(module)\n File \"<frozen importlib._bootstrap_external>\", line 728, in exec_module\n File \"<frozen importlib._bootstrap>\", line 219, in _call_with_frames_removed\n File \"/tmp/ansible_vmware_host_firewall_manager_payload_kf53ugy0/__main__.py\", line 367, in <module>\n File \"/tmp/ansible_vmware_host_firewall_manager_payload_kf53ugy0/__main__.py\", line 363, in main\n File \"/tmp/ansible_vmware_host_firewall_manager_payload_kf53ugy0/__main__.py\", line 238, in ensure\nTypeError: 'NoneType' object is not subscriptable\n",
"module_stdout": "",
"msg": "MODULE FAILURE\nSee stdout/stderr for the exact error",
"rc": 1
}
```
| https://github.com/ansible/ansible/issues/61332 | https://github.com/ansible/ansible/pull/63567 | 358574d57f2b411e820cbf4d00a8249ac8291cb9 | 039c770a9539314e2703781d9c42da20ed5904fb | 2019-08-26T17:45:19Z | python | 2019-10-28T17:01:02Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,311 | ["lib/ansible/module_utils/network/iosxr/facts/interfaces/interfaces.py", "test/integration/targets/iosxr_interfaces/vars/main.yaml"] | Fix iosxr interfaces zuul failure | <!--- Verify first that your issue is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
<!--- Explain the problem briefly below -->
Fix iosxr interfaces zuul failure, which is failing coz of lowercase `loopback` instead of `Loopback` in iosxr. (ref: https://logs.zuul.ansible.com/03/61303/28b181fe1fcb3831516b336923ce39e29942ee50/third-party-check/ansible-test-network-integration-iosxr-python27/80fc31b/controller/ara-report/reports/01641385-035c-4e22-a0bd-fdfbf67a8cb9.html)
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
<!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure -->
iosxr_interfaces
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
devel
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
zuul
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
<!--- Paste example playbooks or commands between quotes below -->
```yaml
```
<!--- HINT: You can paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
iosxr_interfaces should pass as expected
##### ACTUAL RESULTS
<!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) -->
iosxr_interfaces fails
<!--- Paste verbatim command output between quotes -->
```paste below
```
| https://github.com/ansible/ansible/issues/61311 | https://github.com/ansible/ansible/pull/61313 | e536d0e128305f3cfea2bd0cb6ad00c4532b4635 | 30714682c962afd8833b3237f26547c0fc9481d7 | 2019-08-26T11:25:51Z | python | 2019-08-26T16:55:43Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,305 | ["lib/ansible/module_utils/network/ios/config/l3_interfaces/l3_interfaces.py", "lib/ansible/module_utils/network/ios/utils/utils.py", "test/integration/targets/ios_l3_interfaces/tests/cli/_populate_config.yaml", "test/integration/targets/ios_l3_interfaces/tests/cli/merged.yaml", "test/integration/targets/ios_l3_interfaces/tests/cli/overridden.yaml", "test/integration/targets/ios_l3_interfaces/tests/cli/replaced.yaml", "test/integration/targets/ios_l3_interfaces/vars/main.yaml"] | IOS l3 interface tests failing intermittently coz of zuul env issue | <!--- Verify first that your issue is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
<!--- Explain the problem briefly below -->
IOS l3 interface tests failing coz of zuul env issue, replace after assert dict is failing intermittently in diff python version, i.e. sometimes it fails on python27 and other time it fails on python35/37 (ref: https://github.com/ansible/ansible/pull/61103#issuecomment-524646499)
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
<!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure -->
ios_l3_interfaces
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
devel
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
zuul
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
<!--- Paste example playbooks or commands between quotes below -->
```yaml
```
<!--- HINT: You can paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
All test should pass w/o issue
##### ACTUAL RESULTS
<!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) -->
Test fails intermittently
<!--- Paste verbatim command output between quotes -->
```paste below
```
| https://github.com/ansible/ansible/issues/61305 | https://github.com/ansible/ansible/pull/61682 | 01f4081b663ae260f88283aa66ae6fb03bc40ff4 | 2672dc9694f3fe80c7a817f81554a6c8561b065b | 2019-08-26T08:47:47Z | python | 2019-09-04T10:21:05Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,247 | ["lib/ansible/cli/galaxy.py"] | Specification of named galaxy server properties by environment variables not working | ##### SUMMARY
The documentation mentions the ability to specify a galaxy server parameter via the syntax `ANSIBLE_GALAXY_SERVER_{{ id }}_{{ key }}`, but this seems to not be working for the URL of an example of this.
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
lib/ansible/cli/galaxy.py
##### ANSIBLE VERSION
```
ansible --version
ansible 2.9.0.dev0
config file = None
configured module search path = ['/Users/alancoding/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /Users/alancoding/Documents/repos/ansible/lib/ansible
executable location = /Users/alancoding/.virtualenvs/ansible3/bin/ansible
python version = 3.6.5 (default, Apr 25 2018, 14:23:58) [GCC 4.2.1 Compatible Apple LLVM 9.1.0 (clang-902.0.39.1)]
```
##### CONFIGURATION
```
ANSIBLE_NOCOWS(env: ANSIBLE_NOCOWS) = True
```
##### OS / ENVIRONMENT
Mac OS, control machine, also on CentOS
##### STEPS TO REPRODUCE
Run this command
```yaml
ANSIBLE_GALAXY_SERVER_GALAXY_URL=https://galaxy.ansible.com ANSIBLE_GALAXY_SERVER_PRIVATE_GALAXY_URL=https://galaxy-dev.ansible.com ANSIBLE_GALAXY_SERVER_LIST=private_galaxy,galaxy ansible-galaxy collection install -r fallback_not_found/collections/requirements.yml -p dest -vvvv
```
where the content is
```
cat fallback_not_found/collections/requirements.yml
collections:
- name: "chrismeyersfsu.test_things"
- name: "chrismeyersfsu.tower_modules"
```
##### EXPECTED RESULTS
I expect it to attempt to install from the development galaxy server, and then get a 404, and then install from the release galaxy server.
This works if I do not use these environment variables and instead use the config:
```
[galaxy]
server_list = dev_galaxy,galaxy
[galaxy_server.dev_galaxy]
url=https://galaxy-dev.ansible.com
[galaxy_server.galaxy]
url=https://galaxy.ansible.com/
```
The documentation describes this use case here:
https://github.com/jborean93/ansible/blob/devel/docs/docsite/rst/dev_guide/collections_tech_preview.rst
> As well as being defined in the ansible.cfg file, these server options can be defined as an environment variable. The environment variable is in the form ANSIBLE_GALAXY_SERVER_{{ id }}_{{ key }} where {{ id }} is the upper case form of the server identifier and {{ key }} is the key to define. For example I can define token for release_galaxy by setting ANSIBLE_GALAXY_SERVER_RELEASE_GALAXY_TOKEN=secret_token.
The setting for the host is `url`
> url: The URL of the galaxy instance to connect to, this is required.
##### ACTUAL RESULTS
```
ansible-galaxy 2.9.0.dev0
config file = None
configured module search path = ['/Users/alancoding/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /Users/alancoding/Documents/repos/ansible/lib/ansible
executable location = /Users/alancoding/.virtualenvs/ansible3/bin/ansible-galaxy
python version = 3.6.5 (default, Apr 25 2018, 14:23:58) [GCC 4.2.1 Compatible Apple LLVM 9.1.0 (clang-902.0.39.1)]
No config file found; using defaults
ERROR! No setting was provided for required configuration plugin_type: galaxy_server plugin: private_galaxy setting: url
```
I also tried removing "galaxy" from the names, and this has the same result.
```
ANSIBLE_GALAXY_SERVER_FOO_URL=https://galaxy.ansible.com ANSIBLE_GALAXY_SERVER_BAR_URL=https://galaxy-dev.ansible.com ANSIBLE_GALAXY_SERVER_LIST=bar,foo ansible-galaxy collection install -r fallback_not_found/collections/requirements.yml -p dest -vvvv
ansible-galaxy 2.9.0.dev0
config file = None
configured module search path = ['/Users/alancoding/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /Users/alancoding/Documents/repos/ansible/lib/ansible
executable location = /Users/alancoding/.virtualenvs/ansible3/bin/ansible-galaxy
python version = 3.6.5 (default, Apr 25 2018, 14:23:58) [GCC 4.2.1 Compatible Apple LLVM 9.1.0 (clang-902.0.39.1)]
No config file found; using defaults
ERROR! No setting was provided for required configuration plugin_type: galaxy_server plugin: bar setting: url
```
Ping @jborean93 @chrismeyersfsu @ryanpetrello
We do _not_ rate this as a Tower blocker, because the `ansible.cfg` specification of parameters is known to work, and we will begin to design around that. | https://github.com/ansible/ansible/issues/61247 | https://github.com/ansible/ansible/pull/61294 | 265fcaac40dcc28fcb708cad78df5b0042ded0e8 | 9786e2b55919f51997524b16bbf91f98058e5d47 | 2019-08-23T20:45:57Z | python | 2019-08-25T21:11:35Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,244 | ["lib/ansible/module_utils/network/eos/config/vlans/vlans.py", "test/integration/targets/eos_vlans/tests/cli/idempotent.yaml"] | eos_vlans not reporting state parameter | ##### SUMMARY
Arista vEOS reports a state (active) but the eos_facts module is returning nothing
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
eos_facts
eos_vlans
##### ANSIBLE VERSION
```paste below
[student1@ansible ~]$ ansible --version
ansible 2.9.0.dev0
config file = /home/student1/.ansible.cfg
configured module search path = [u'/home/student1/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /home/student1/.local/lib/python2.7/site-packages/ansible
executable location = /usr/bin/ansible
python version = 2.7.5 (default, Jun 11 2019, 14:33:56) [GCC 4.8.5 20150623 (Red Hat 4.8.5-39)]
```
##### CONFIGURATION
```paste below
[student1@ansible ~]$ ansible-config dump --only-changed
DEFAULT_HOST_LIST(/home/student1/.ansible.cfg) = [u'/home/student1/networking-workshop/lab_inventory/hosts']
DEFAULT_STDOUT_CALLBACK(/home/student1/.ansible.cfg) = yaml
DEFAULT_TIMEOUT(/home/student1/.ansible.cfg) = 60
DEPRECATION_WARNINGS(/home/student1/.ansible.cfg) = False
HOST_KEY_CHECKING(/home/student1/.ansible.cfg) = False
PERSISTENT_COMMAND_TIMEOUT(/home/student1/.ansible.cfg) = 60
PERSISTENT_CONNECT_TIMEOUT(/home/student1/.ansible.cfg) = 60
RETRY_FILES_ENABLED(/home/student1/.ansible.cfg) = False
```
##### OS / ENVIRONMENT
```
[student1@ansible ~]$ cat /etc/*release
NAME="Red Hat Enterprise Linux Server"
VERSION="7.6 (Maipo)"
ID="rhel"
ID_LIKE="fedora"
VARIANT="Server"
VARIANT_ID="server"
VERSION_ID="7.6"
PRETTY_NAME="Red Hat Enterprise Linux Server 7.6 (Maipo)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:7.6:GA:server"
HOME_URL="https://www.redhat.com/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 7"
REDHAT_BUGZILLA_PRODUCT_VERSION=7.6
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="7.6"
Red Hat Enterprise Linux Server release 7.6 (Maipo)
Red Hat Enterprise Linux Server release 7.6 (Maipo)
```
##### STEPS TO REPRODUCE
```yaml
[student1@ansible ~]$ cat eos_vlans.yml
---
- hosts: rtr2
gather_facts: false
tasks:
- name: grab info
eos_facts:
gather_subset: min
gather_network_resources: vlans
- debug:
var: ansible_network_resources
```
<!--- HINT: You can paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
```state: active``` for corresponding vlans
##### ACTUAL RESULTS
playbook output
```
[student1@ansible ~]$ ansible-playbook eos_vlans.yml
PLAY [rtr2] *********************************************************************************************************************
TASK [grab info] ****************************************************************************************************************
[WARNING]: default value for `gather_subset` will be changed to `min` from `!config` v2.11 onwards
ok: [rtr2]
TASK [debug] ********************************************************************************************************************
ok: [rtr2] =>
ansible_network_resources:
vlans:
- vlan_id: 2
- vlan_id: 3
- vlan_id: 4
- vlan_id: 5
- vlan_id: 100
PLAY RECAP **********************************************************************************************************************
rtr2 : ok=2 changed=0 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0
```
output from switch clearly shows state
```paste below
[student1@ansible ~]$ ssh rtr2
Last login: Fri Aug 23 19:44:33 2019 from 18.222.116.40
rtr2>en
rtr2#show vlan
VLAN Name Status Ports
----- -------------------------------- --------- -------------------------------
1 default active
2 VLAN0002 active
3 VLAN0003 active
4 VLAN0004 active
5 VLAN0005 active
100 VLAN0100 active
```
| https://github.com/ansible/ansible/issues/61244 | https://github.com/ansible/ansible/pull/61432 | b20bfc104863e7b2d90c1a639ae686dbd290eb84 | 841d204d0d90ed6dc03715ae8affcb045c5cb190 | 2019-08-23T19:50:10Z | python | 2019-08-28T17:53:33Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,236 | ["lib/ansible/module_utils/basic.py", "lib/ansible/module_utils/urls.py", "lib/ansible/modules/files/copy.py", "lib/ansible/modules/files/iso_extract.py", "lib/ansible/modules/net_tools/basics/get_url.py", "lib/ansible/modules/net_tools/basics/uri.py", "lib/ansible/plugins/doc_fragments/url.py"] | Consider removing `thirsty` alias from the copy module (only the copy module) | <!--- Verify first that your feature was not already discussed on GitHub -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
When I read the `copy` documentation, I couldn't work out what it meant. Unfortunately, this meant it sounded like it might be a weird sex joke.
It doesn't sound like a big problem, but in an ideal world, I think we should prefer to avoid weird sex jokes in an alias for a parameter called `force`.
##### ISSUE TYPE
- Feature Idea
##### COMPONENT NAME
copy
##### ADDITIONAL INFORMATION
Issue search tells me "thirsty" was added as an option to the `get_url` module. In that context, it is appropriate. But in the context of the `copy` module, it does not make sense, because `copy` only works in the upload direction.
The first three pages of Google Search results (Ansible thirsty) show people using "thirsty" for downloads only, not uploads. Similarly for GitHub code search (copy thirsty language:YAML). | https://github.com/ansible/ansible/issues/61236 | https://github.com/ansible/ansible/pull/61245 | 73767778e01b3d682878e60d3ddbd1bf77bea229 | 8d167bdaef8469e0998996317023d3906a293485 | 2019-08-23T16:34:41Z | python | 2019-08-28T13:27:08Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,234 | ["changelogs/fragments/61234-yum-dnf-version-comp-doc.yml", "lib/ansible/modules/dnf.py", "lib/ansible/modules/yum.py"] | Yum and dnf module comparison operators not documented | ##### Summary
Document " <, >, <=, => " operators in name parameter of yum/dnf module. Currently the documentation does not mention that comparison operators are available, but they do work.
##### ISSUE TYPE
- Feature Idea
##### COMPONENT NAME
yum/dnf module
##### ADDITIONAL INFORMATION
The value operators work currently in the yum/dnf modules
```
yum :
name: "pkg >= 1"
state: present
```
Yum/dnf will determine the version available and install it if it matches the comparison operator
| https://github.com/ansible/ansible/issues/61234 | https://github.com/ansible/ansible/pull/72763 | e7dee73774b0b436551e4993ba917eec1e03af2d | 0044091a055dd9cd448f7639a65b7e8cc3dacbf1 | 2019-08-23T15:36:24Z | python | 2020-12-11T15:31:19Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,233 | ["lib/ansible/plugins/doc_fragments/template_common.py"] | Template action does not recursively evaluate variables any more | <!--- Verify first that your improvement is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
Templates do not appear to be evaluated recursively anymore (see #4638). I don't know when it changed. I am using Ansible -devel or 2.8. If it helps, here is the reproducer from issue #4638:
> [playbook.yml]
>
> ```
> ---
> - name: "test raw template output"
> hosts: localhost
>
> vars:
> myvar: "foo"
>
> tasks:
> - local_action: template src="mytemplate.j2" dest="/tmp/myoutput.txt"
>
> ```
>
> [mytemplate.j2]
>
> ```
> Test: Preserve curly braces, and NOT perform variable substitution:
>
> First Attempt:
> {% raw %}
> - { include: "{{ myvar }}" }
> {% endraw %}
> ```
>
> [/tmp/myoutput.txt]
>
> ```
> Test: Preserve curly braces, and NOT perform variable substitution:
>
>
> First Attempt:
>
> - { include: "foo" }
> ```
>
> NOTE: template output performs variable substitution even inside the {% raw %} block.
and here is the output *I* got:
```
Test: Preserve curly braces, and NOT perform variable substitution:
First Attempt:
- { include: "{{ myvar }}" }
```
At least, I really hope this is a documentation bug. I think the old behaviour was a bad idea. I would not like Ansible to go back to it.
##### ISSUE TYPE
- Documentation Report
##### COMPONENT NAME
<!--- Write the short name of the rst file, module, plugin, task or feature below, use your best guess if unsure -->
template
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```
ansible 2.9.0.dev0
config file = /etc/ansible/ansible.cfg
configured module search path = [u'/home/alan-sysop/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /home/alan-sysop/src/ansible/lib/ansible
executable location = /home/alan-sysop/src/ansible/bin/ansible
python version = 2.7.16 (default, Apr 30 2019, 15:54:43) [GCC 9.0.1 20190312 (Red Hat 9.0.1-0.10)]
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
`ansible-config dump --only-changed` shows no output at all.
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. OS version, browser, etc. -->
Fedora Workstation 30
##### ADDITIONAL INFORMATION
I'm hoping this is all ancient history now. If so, we can simply remove the sentence in question:
> * Using raw/endraw in Jinja2 will not work as you expect because templates in Ansible are recursively evaluated.
https://docs.ansible.com/ansible/latest/modules/template_module.html#notes | https://github.com/ansible/ansible/issues/61233 | https://github.com/ansible/ansible/pull/76955 | 0d5401d950346d4398b1f8e1ab80e63e33a8266b | 8582df36c5931a488d36bc2efaf8fa5324668538 | 2019-08-23T15:07:11Z | python | 2022-02-08T15:26:37Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,220 | ["lib/ansible/modules/cloud/vmware/vmware_category.py", "test/integration/targets/vmware_category/aliases", "test/integration/targets/vmware_category/tasks/associable_obj_types.yml", "test/integration/targets/vmware_category/tasks/main.yml"] | vmware_category add "Associable Object Types" functionality | ##### SUMMARY
Can functionality be added so that "Associable Object Types" can be configured for a tag category please?
##### ISSUE TYPE
- Feature Idea
##### COMPONENT NAME
vmware_category
##### ADDITIONAL INFORMATION
Perhaps the module could be extended to include a list, examples below;
```
- name: 'Create a Category'
connection: 'local'
vmware_category:
hostname: '{{ ansible_host }}'
username: '{{ ansible_vcenter_username }}'
password: '{{ ansible_vcenter_password }}'
category_name: "sas_luns"
category_description: "SAS LUNS"
category_cardinality: 'multiple'
associable_object_types:
- Datastore
- Datastore Cluster
state: present
validate_certs: '{{ validate_certs }}'
- name: 'Create a Category'
connection: 'local'
vmware_category:
hostname: '{{ ansible_host }}'
username: '{{ ansible_vcenter_username }}'
password: '{{ ansible_vcenter_password }}'
category_name: "Region 1"
category_description: "Region"
category_cardinality: 'multiple'
associable_object_types:
- All objects
state: present
validate_certs: '{{ validate_certs }}'
```
The type of Associable Object Types in vSphere 6.7 are:
All objects
Folder
Cluster
Datacenter
Datastore
Datastore Cluster
Distributed Port Group
Distributed Switch
Host
Content Library
Library item
Network
Resource Pool
vApp
Virtual Machine
| https://github.com/ansible/ansible/issues/61220 | https://github.com/ansible/ansible/pull/62347 | 24b8b629b9a608583262467bbdb63ed828530c78 | 19220a0607437ff29ccccdd67f5012cca0eee2f1 | 2019-08-23T11:40:12Z | python | 2019-12-11T08:15:07Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,218 | ["lib/ansible/playbook/included_file.py", "test/integration/targets/loop_control/extended.yml", "test/integration/targets/loop_control/inner.yml", "test/integration/targets/loop_control/runme.sh"] | ansible_loop undefined with extended loop_control in an include | ##### SUMMARY
Setting `extended: yes` in `loop_control` doesn't provide `ansible_loop` inside the loop.
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
loop_control
##### ANSIBLE VERSION
```
ansible 2.9.0.dev0
config file = None
configured module search path = ['/home/kustodian/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /home/kustodian/git/github/ansible/lib/ansible
executable location = /home/kustodian/git/github/ansible/bin/ansible
python version = 3.7.4 (default, Jul 16 2019, 07:12:58) [GCC 9.1.0]
```
This also doesn't work on 2.8.4
##### CONFIGURATION
```
```
##### OS / ENVIRONMENT
ArchLinux
##### STEPS TO REPRODUCE
Create two files:
```yaml
# play.yml
---
- hosts: localhost
connection: local
tasks:
- include_tasks: inner.yml
loop:
- 1
- 2
- 3
loop_control:
extended: yes
```
```
# inner.yml
- debug:
var: ansible_loop
```
and run:
```
ansible-playbook play.yml -i localhost,
```
##### EXPECTED RESULTS
Ansible should print the value of `ansible_loop` three times.
##### ACTUAL RESULTS
It actually prints that `ansible_loop` is undefined:
```
$ ansible-playbook play.yml -i localhost,
PLAY [localhost] *******************************************************************************************************************************************************************************************
TASK [Gathering Facts] *************************************************************************************************************************************************************************************
ok: [localhost]
TASK [include_tasks] ***************************************************************************************************************************************************************************************
included: /tmp/inner.yml for localhost
included: /tmp/inner.yml for localhost
included: /tmp/inner.yml for localhost
TASK [debug] ***********************************************************************************************************************************************************************************************
ok: [localhost] => {
"ansible_loop": "VARIABLE IS NOT DEFINED!"
}
TASK [debug] ***********************************************************************************************************************************************************************************************
ok: [localhost] => {
"ansible_loop": "VARIABLE IS NOT DEFINED!"
}
TASK [debug] ***********************************************************************************************************************************************************************************************
ok: [localhost] => {
"ansible_loop": "VARIABLE IS NOT DEFINED!"
}
PLAY RECAP *************************************************************************************************************************************************************************************************
localhost : ok=7 changed=0 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0
```
| https://github.com/ansible/ansible/issues/61218 | https://github.com/ansible/ansible/pull/61231 | 80b73712a9130eabe441f9acef2f4f4453dfbe84 | a213b9160c7902122d20f05b2fa27a15cd541f4a | 2019-08-23T09:54:07Z | python | 2019-08-27T17:09:56Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,195 | ["changelogs/fragments/61284-ec2_asg-idempotency.yml", "hacking/aws_config/testing_policies/compute-policy.json", "lib/ansible/modules/cloud/amazon/ec2_asg.py", "test/integration/targets/ec2_asg/tasks/main.yml"] | Setting ec2_asg `metrics_collection: yes` results in module always reporting modifications | <!--- Verify first that your issue is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
<!--- Explain the problem briefly below -->
Similar to #61085, there is a comparison bug which is encountered when the module attempts to compare the value of "EnabledMetrics". The ordering of the input list might not match the API response's ordering for the existing ASG, which will cause the module to believe the ASG has been modified, even if it hasn't. This bug is only encountered when `metrics_collection: yes`.
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
<!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure -->
ec2_asg
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
2.8.4
```
##### CONFIGURATION
N/A
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
Arch, Red Hat 7, CentOS 7
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
Set `metrics_collection: yes`, run task multiple times without any modification. Since the API response ordering does not match the default value, the resource will always appear as "modified".
<!--- HINT: You can paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
If no changes are introduced, the task should not report any modifications.
##### ACTUAL RESULTS
Ansible reports modifications to the ASGs. | https://github.com/ansible/ansible/issues/61195 | https://github.com/ansible/ansible/pull/61284 | d7604844c2a489bb13216dd6340345ac2bb1df7f | b8650c0a50eb76aa1146ea7119d3451e2253037f | 2019-08-22T19:34:22Z | python | 2019-09-06T19:48:40Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,185 | ["changelogs/fragments/61185-basic.py-fix-check_mode.yaml", "lib/ansible/module_utils/basic.py", "test/units/module_utils/basic/test_set_mode_if_different.py"] | htpasswd module does not properly handle creating files in check mode | ##### SUMMARY
When in check mode, the check_file_attrs function is still called. This calls `module.set_fs_attributes_if_different,` which eventually raises an exception in `module.set_mode_if_different` if the file doesn't exist. This situation can occur when running in check mode when the destination file does not yet exist, even if `create` is set to `yes`.
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
htpasswd
##### ANSIBLE VERSION
```paste below
ansible 2.8.0
config file = /Users/matthieu/dev/ansible/ansible.cfg
configured module search path = ['/Users/matthieu/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /Users/matthieu/.pyenv/versions/3.6.3/envs/ansible/lib/python3.6/site-packages/ansible
executable location = /Users/matthieu/.pyenv/versions/ansible/bin/ansible
python version = 3.6.3 (default, Oct 9 2017, 18:08:57) [GCC 4.2.1 Compatible Apple LLVM 9.0.0 (clang-900.0.37)]
```
##### CONFIGURATION
```paste below
ANSIBLE_PIPELINING(/Users/matthieu/dev/ansible/ansible.cfg) = True
DEFAULT_LOG_PATH(/Users/matthieu/dev/ansible/ansible.cfg) = /Users/matthieu/dev/ansible/ansible.log
DEFAULT_REMOTE_USER(/Users/matthieu/dev/ansible/ansible.cfg) = root
```
##### OS / ENVIRONMENT
From Mac to Linux 16.04
##### STEPS TO REPRODUCE
Run a playbook in check mode that contains this task:
```yaml
- name: Set up basic auth credentials file
htpasswd:
create: yes
crypt_scheme: apr_md5_crypt
name: "testuser"
password: "testpass"
path: "/tmp/thisfiledoesnotexist.htpasswd"
state: present
```
Please note a very similar bug was already fixed in v2.4 https://github.com/ansible/ansible/issues/32676
It may be worth to write a test case for this scenario...
##### EXPECTED RESULTS
The check run should complete successfully with a note that the file will be created.
##### ACTUAL RESULTS
I get the following error message:
`[Errno 2] No such file or directory: '/tmp/thisfiledoesnotexist.htpasswd'`
This is what I get when I run ansible-playbook with -vvv:
```
The full traceback is:
WARNING: The below traceback may *not* be related to the actual failure.
File "/tmp/ansible_htpasswd_payload_b44M9M/__main__.py", line 268, in main
check_file_attrs(module, changed, msg)
File "/tmp/ansible_htpasswd_payload_b44M9M/__main__.py", line 192, in check_file_attrs
if module.set_fs_attributes_if_different(file_args, False):
File "/tmp/ansible_htpasswd_payload_b44M9M/ansible_htpasswd_payload.zip/ansible/module_utils/basic.py", line 1339, in set_fs_attributes_if_different
file_args['path'], file_args['mode'], changed, diff, expand
File "/tmp/ansible_htpasswd_payload_b44M9M/ansible_htpasswd_payload.zip/ansible/module_utils/basic.py", line 1063, in set_mode_if_different
path_stat = os.lstat(b_path)
```
| https://github.com/ansible/ansible/issues/61185 | https://github.com/ansible/ansible/pull/64279 | b043afa025063fb452c8e01736c919cd2e7ef410 | 7099657dd7279ef2989d601251f46e7407a86fa6 | 2019-08-22T16:40:49Z | python | 2021-04-28T08:17:03Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,085 | ["changelogs/fragments/61284-ec2_asg-idempotency.yml", "hacking/aws_config/testing_policies/compute-policy.json", "lib/ansible/modules/cloud/amazon/ec2_asg.py", "test/integration/targets/ec2_asg/tasks/main.yml"] | ec2_asg tagging results in "modified" status if tags are not alphabetized | <!--- Verify first that your issue is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
When the ec2_asg module attempts to evaluate whether tags for an ASG have changed, it compares the input list of tags (in the order given) to the API result (in the order returned by the API, A-Za-z). If the ordering is not the same (non-alphabetical input), the module believes that modifications have been made, and issues API calls to replace the tags.
This is due to the [use](https://github.com/ansible/ansible/blob/devel/lib/ansible/modules/cloud/amazon/ec2_asg.py#L1047) of `zip()` without respect to key ordering. This can be resolved by sorting the input dictionaries by key prior to `zip()`, or by switching to something [like](https://github.com/ansible/ansible/blob/73e171fd946b74089a99051858d8d49e561dea41/lib/ansible/module_utils/ec2.py#L706) `compare_aws_tags()` from `ansible.module_utils.ec2`.
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
<!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure -->
ec2_asg
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
2.8.4
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
N/A
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
N/A
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
<!--- Paste example playbooks or commands between quotes below -->
```yaml
- ec2_asg:
name: special
load_balancers: [ 'lb1', 'lb2' ]
availability_zones: [ 'eu-west-1a', 'eu-west-1b' ]
launch_config_name: 'lc-1'
min_size: 1
max_size: 10
desired_capacity: 5
vpc_zone_identifier: [ 'subnet-abcd1234', 'subnet-1a2b3c4d' ]
tags:
- environment: production
Propagate_at_launch: no
```
This will always show modification, as the tags are listed in an order different than the API response.
<!--- HINT: You can paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
Tags are evaluated by matching keys, without regard to alphabetical input ordering
##### ACTUAL RESULTS
Ansible shows modifications have occurred and updates the ASG's tags, even though no true modifications have been made. | https://github.com/ansible/ansible/issues/61085 | https://github.com/ansible/ansible/pull/61284 | d7604844c2a489bb13216dd6340345ac2bb1df7f | b8650c0a50eb76aa1146ea7119d3451e2253037f | 2019-08-22T02:48:10Z | python | 2019-09-06T19:48:40Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,084 | ["changelogs/fragments/61279-ec2_launch_template-output.yml", "lib/ansible/modules/cloud/amazon/ec2_launch_template.py", "test/integration/targets/ec2_launch_template/playbooks/roles/ec2_launch_template/tasks/main.yml", "test/integration/targets/ec2_launch_template/playbooks/roles/ec2_launch_template/tasks/versions.yml"] | ec2_launch_template return values do not conform to documentation | <!--- Verify first that your issue is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
The ec2_launch_template documentation states that it provides two return values, other than the common return values. This includes:
Key | Returned | Description
-- | -- | --
default_version integer | when state=present | The version that will be used if only the template name is specified. Often this is the same as the latest version, but not always.
latest_version integer | when state=present | Latest available version of the launch template
However, the function `format_module_output`, which is [used](https://github.com/ansible/ansible/blob/272dceef4258fdfdc90281ce1d0b02236f16a797/lib/ansible/modules/cloud/amazon/ec2_launch_template.py#L499) to generate this module's output, stores default_template and latest_template, not default_version and latest_version.
```python
output['default_template'] = [
v for v in template_versions
if v.get('default_version')
][0]
output['latest_template'] = [
v for v in template_versions
if (
v.get('version_number') and
int(v['version_number']) == int(template['latest_version_number'])
)
][0]
return output
```
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
ec2_launch_template
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
2.8.4
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
N/A
##### OS / ENVIRONMENT
N/A
##### STEPS TO REPRODUCE
1. Store results of ec2_launch_template
2. Examine the contents of the results, which does not conform to the documentation.
##### EXPECTED RESULTS
Either two integer key/values should be available, or the documentation should correctly indicate that the output includes default_template and latest_template.
##### ACTUAL RESULTS
default_template and latest_template exist in the results, default_version and latest_version do not.
| https://github.com/ansible/ansible/issues/61084 | https://github.com/ansible/ansible/pull/61279 | 791e9dabe3c1cb50a315d82fbb7252f4a38885f6 | c40832af482c3cc7b0c291ead5228ca582593419 | 2019-08-22T02:29:04Z | python | 2019-12-18T20:53:57Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,081 | ["lib/ansible/modules/cloud/openstack/os_loadbalancer.py"] | os_loadbalancer: absent doesn't work | <!--- Verify first that your issue is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
<!--- Explain the problem briefly below -->
OpenStack load balancer deletion failed:
```
TASK [delete lb] ***************************************************************************************************************************************************************************************************************************
fatal: [localhost]: FAILED! => {
"changed": false,
"extra_data": null
}
MSG:
No LoadBalancer found for 730c776d-d6ac-448c-95f8-4727491b297d: Client Error for url: http://192.168.206.8/load-balancer/v2.0/lbaas/loadbalancers/730c776d-d6ac-448c-95f8-4727491b297d, Not Found
```
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
<!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure -->
os_loadbalancer
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
ansible 2.9.0.dev0
config file = /etc/ansible/ansible.cfg
configured module search path = [u'/home/lingxiankong/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /home/lingxiankong/code/github/ansible/lib/ansible
executable location = /home/lingxiankong/code/github/ansible/bin/ansible
python version = 2.7.12 (default, Nov 12 2018, 14:36:49) [GCC 5.4.0 20160609]
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
DEFAULT_STDOUT_CALLBACK(/etc/ansible/ansible.cfg) = debug
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
```
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.5 LTS
Release: 16.04
Codename: xenial
```
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
<!--- Paste example playbooks or commands between quotes below -->
```yaml
- name: test delete lb
connection: local
hosts: localhost
tasks:
- name: delete lb
os_loadbalancer:
name: lingxiank8s-lb
state: absent
wait: yes
timeout: 600
```
<!--- HINT: You can paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
the load balancer is deleted successfully.
##### ACTUAL RESULTS
<!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) -->
<!--- Paste verbatim command output between quotes -->
```paste below
TASK [delete lb] ***************************************************************************************************************************************************************************************************************************
fatal: [localhost]: FAILED! => {
"changed": false,
"extra_data": null
}
MSG:
No LoadBalancer found for 730c776d-d6ac-448c-95f8-4727491b297d: Client Error for url: http://192.168.206.8/load-balancer/v2.0/lbaas/loadbalancers/730c776d-d6ac-448c-95f8-4727491b297d, Not Found
```
| https://github.com/ansible/ansible/issues/61081 | https://github.com/ansible/ansible/pull/61083 | eeb2fd35d1cd21839eab95c31910c907639c6f24 | a53ec6af87ab4a8ada9b4cc40ad5444e1832bac4 | 2019-08-22T02:09:10Z | python | 2019-08-22T13:20:32Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,068 | ["lib/ansible/config/module_defaults.yml"] | module_defaults don't apply to aliased modules | ##### SUMMARY
If you use module_defaults (especially on a group) but call the module by one of its aliases then it fails to pick up the defaults
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
lib/ansible/config/module_defaults.yml
##### ANSIBLE VERSION
Triggered this against devel (because _facts was renamed to _info)
##### CONFIGURATION
```
DEFAULT_CALLBACK_WHITELIST(/home/mchappel/.ansible.cfg) = [u'timer', u'profile_tasks']
HOST_KEY_CHECKING(/home/mchappel/.ansible.cfg) = False
RETRY_FILES_ENABLED(/home/mchappel/.ansible.cfg) = False
```
##### OS / ENVIRONMENT
RHEL7
##### STEPS TO REPRODUCE
```
- name: Run ec2_asg integration tests.
module_defaults:
group/aws:
aws_access_key: "{{ aws_access_key }}"
aws_secret_key: "{{ aws_secret_key }}"
security_token: "{{ security_token | default(omit) }}"
region: "{{ aws_region }}"
block:
- name: Find AMI to use
ec2_ami_info:
owners: 'amazon'
filters:
name: '{{ ec2_ami_name }}'
register: ec2_amis
- name: Find AMI to use
ec2_ami_facts:
owners: 'amazon'
filters:
name: '{{ ec2_ami_name }}'
register: ec2_amis
```
##### EXPECTED RESULTS
ec2_ami_facts and ec2_ami_info should both use the defaults.
##### ACTUAL RESULTS
ec2_ami_info uses the module_defaults, ec2_ami_facts doesn't. | https://github.com/ansible/ansible/issues/61068 | https://github.com/ansible/ansible/pull/61203 | 53df4d8186e6cc55ed94abc807b066cc9ac5a758 | 1d405fdd60dc578fa2b3ea24f87dd7b4a9ebea5b | 2019-08-21T20:01:44Z | python | 2019-08-26T14:05:57Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 61,002 | ["changelogs/fragments/64906-always-delegate-fact-prefixes.yml", "lib/ansible/plugins/strategy/__init__.py"] | discovered_interpreter_python is not fetched for delegated hosts | ##### SUMMARY
I'm running a playbook on a host on F30 where `discovered_interpreter_python` is found to be `/usr/bin/python3`. Later the playbook I delegate tasks to another host which happen to run using the same interpreter without redoing the discovery and contrary to currently cached value.
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
discovered_interpreter_python
##### ANSIBLE VERSION
```paste below
ansible 2.8.4
config file = /home/duck/Projects/oVirt/gerrit_infra-ansible/ansible.cfg
configured module search path = ['/home/duck/Projects/oVirt/gerrit_infra-ansible/library']
ansible python module location = /home/duck/.local/lib/python3.7/site-packages/ansible
executable location = /home/duck/.local/bin/ansible
python version = 3.7.4 (default, Jul 11 2019, 10:43:21) [GCC 8.3.0]
```
##### CONFIGURATION
```paste below
ANSIBLE_FORCE_COLOR(env: ANSIBLE_FORCE_COLOR) = True
ANSIBLE_PIPELINING(/home/duck/Projects/oVirt/gerrit_infra-ansible/ansible.cfg) = True
ANSIBLE_SSH_ARGS(/home/duck/Projects/oVirt/gerrit_infra-ansible/ansible.cfg) = -o ControlMaster=auto -o ControlPersist=30m
CACHE_PLUGIN(/home/duck/Projects/oVirt/gerrit_infra-ansible/ansible.cfg) = jsonfile
CACHE_PLUGIN_CONNECTION(/home/duck/Projects/oVirt/gerrit_infra-ansible/ansible.cfg) = ./facts_cache
CACHE_PLUGIN_TIMEOUT(/home/duck/Projects/oVirt/gerrit_infra-ansible/ansible.cfg) = 86400
DEFAULT_ACTION_PLUGIN_PATH(/home/duck/Projects/oVirt/gerrit_infra-ansible/ansible.cfg) = ['/home/duck/Projects/oVirt/gerrit_infra-ansible/plugins/a
DEFAULT_CALLBACK_PLUGIN_PATH(/home/duck/Projects/oVirt/gerrit_infra-ansible/ansible.cfg) = ['/home/duck/Projects/oVirt/gerrit_infra-ansible/plugins
DEFAULT_CONNECTION_PLUGIN_PATH(/home/duck/Projects/oVirt/gerrit_infra-ansible/ansible.cfg) = ['/home/duck/Projects/oVirt/gerrit_infra-ansible/plugi
DEFAULT_FILTER_PLUGIN_PATH(/home/duck/Projects/oVirt/gerrit_infra-ansible/ansible.cfg) = ['/home/duck/Projects/oVirt/gerrit_infra-ansible/plugins/f
DEFAULT_FORKS(/home/duck/Projects/oVirt/gerrit_infra-ansible/ansible.cfg) = 10
DEFAULT_GATHERING(/home/duck/Projects/oVirt/gerrit_infra-ansible/ansible.cfg) = smart
DEFAULT_HASH_BEHAVIOUR(/home/duck/Projects/oVirt/gerrit_infra-ansible/ansible.cfg) = merge
DEFAULT_HOST_LIST(/home/duck/Projects/oVirt/gerrit_infra-ansible/ansible.cfg) = ['/home/duck/Projects/oVirt/gerrit_infra-ansible/hosts.yml']
DEFAULT_LOOKUP_PLUGIN_PATH(/home/duck/Projects/oVirt/gerrit_infra-ansible/ansible.cfg) = ['/home/duck/Projects/oVirt/gerrit_infra-ansible/plugins/l
DEFAULT_MANAGED_STR(/home/duck/Projects/oVirt/gerrit_infra-ansible/ansible.cfg) = Ansible managed
DEFAULT_MODULE_PATH(/home/duck/Projects/oVirt/gerrit_infra-ansible/ansible.cfg) = ['/home/duck/Projects/oVirt/gerrit_infra-ansible/library']
DEFAULT_ROLES_PATH(/home/duck/Projects/oVirt/gerrit_infra-ansible/ansible.cfg) = ['/home/duck/Projects/oVirt/gerrit_infra-ansible/roles']
DEFAULT_STRATEGY_PLUGIN_PATH(/home/duck/Projects/oVirt/gerrit_infra-ansible/ansible.cfg) = ['/home/duck/Projects/oVirt/gerrit_infra-ansible/plugins
DEFAULT_TIMEOUT(/home/duck/Projects/oVirt/gerrit_infra-ansible/ansible.cfg) = 40
DEFAULT_VARS_PLUGIN_PATH(/home/duck/Projects/oVirt/gerrit_infra-ansible/ansible.cfg) = ['/home/duck/Projects/oVirt/gerrit_infra-ansible/plugins/var
DEFAULT_VAULT_PASSWORD_FILE(env: ANSIBLE_VAULT_PASSWORD_FILE) = /somewhere
ERROR_ON_MISSING_HANDLER(/home/duck/Projects/oVirt/gerrit_infra-ansible/ansible.cfg) = True
INTERPRETER_PYTHON(/home/duck/Projects/oVirt/gerrit_infra-ansible/ansible.cfg) = auto
PARAMIKO_HOST_KEY_AUTO_ADD(/home/duck/Projects/oVirt/gerrit_infra-ansible/ansible.cfg) = True
PERSISTENT_CONNECT_TIMEOUT(/home/duck/Projects/oVirt/gerrit_infra-ansible/ansible.cfg) = 1800
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
##### STEPS TO REPRODUCE
```yaml
---
- hosts: ovirt-web-builder.int.osci.io
tasks:
- name: Get facts for the other side
setup:
delegate_to: www.ovirt.org
delegate_facts: True
```
##### EXPECTED RESULTS
Ansible should use the value in my cache (see below) or if expired initiate a discovery for www.ovirt.org instead of using the same interpreter as the target host.
##### ACTUAL RESULTS
```paste below
PLAY [ovirt-web-builder.int.osci.io] **************************************************************************************************************
TASK [Get facts for the other side] ***************************************************************************************************************
fatal: [ovirt-web-builder.int.osci.io -> 8.43.85.224]: FAILED! => {"changed": false, "module_stderr": "/bin/sh: /usr/bin/python3: No such file or directory\n", "module_stdout": "", "msg": "The module failed to execute correctly, you probably need to set the interpreter.\nSee stdout/stderr for the exact error", "rc": 127}
PLAY RECAP ****************************************************************************************************************************************
ovirt-web-builder.int.osci.io : ok=0 changed=0 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0
```
Please not my cache:
```
$ grep discovered_interpreter_python facts_cache/www.ovirt.org
"discovered_interpreter_python": "/usr/bin/python",
```
moving the cache file aside does not change the behavior.
doing a setup manually works and discover the right interpreter:
```
$ ansible www.ovirt.org -m setup | grep discovered_interpreter_python
"discovered_interpreter_python": "/usr/bin/python",
```
Also the value of `interpreter_python` in `ansible.cfg` does not change anything.
Of course I can force the value of `ansible_python_interpreter` and everything works fine, but why would I do that since we now have a magic autodetection? This is also a regression for a perfectly working playbook.
| https://github.com/ansible/ansible/issues/61002 | https://github.com/ansible/ansible/pull/64906 | 318d5606c1d7e8be69b647a77f044b3532f30d7e | 123c624b28398c10864be5238dfdd44c524564a0 | 2019-08-21T09:43:41Z | python | 2020-04-06T20:09:00Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 60,989 | ["lib/ansible/modules/windows/win_scheduled_task.ps1", "lib/ansible/modules/windows/win_scheduled_task.py", "test/integration/targets/win_scheduled_task/tasks/failures.yml"] | win_scheduled_task should support gMSA principals | <!--- Verify first that your feature was not already discussed on GitHub -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
A [Group Managed Service Account or gMSA](https://techcommunity.microsoft.com/t5/Core-Infrastructure-and-Security/Windows-Server-2012-Group-Managed-Service-Accounts/ba-p/255910) is a special type of service account in Active Directory that has its password managed automatically and can be used across multiple servers. The password is not known to administrators, and services, applications, and scheduled tasks that run as this account are able to automatically retrieve the password for the account.
Scheduled Tasks can run as gMSA, by setting a `logon_type` of `password` without actually supplying a password.
The `win_scheduled_task` module enforces that a password is supplied when the logon type is `password`, but the code otherwise would work as is.
##### ISSUE TYPE
- Feature Idea
##### COMPONENT NAME
<!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure -->
win_scheduled_task
##### ADDITIONAL INFORMATION
<!--- Describe how the feature would be used, why it is needed and what it would solve -->
<!--- Paste example playbooks or commands between quotes below -->
```yaml
- name: Task with gMSA
win_scheduled_task:
name: TaskName2
username: DOMAIN\gMsaSvcAcct$
logon_type: password
```
<!--- HINT: You can also paste gist.github.com links for larger files -->
| https://github.com/ansible/ansible/issues/60989 | https://github.com/ansible/ansible/pull/60990 | 0914cdb345d4af31c3bb58af064217653567eb1a | eaa68489327cfacbf1d29efb363faa3ea11c0315 | 2019-08-21T04:47:30Z | python | 2019-08-27T22:44:45Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 60,968 | ["lib/ansible/modules/system/seport.py"] | seport: Doesn't support numerical ports | ##### SUMMARY
If `seport` is given a numerical port, or list of numerical ports. It fails to parse. This is contrary to the documentation examples.
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
seport
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
ansible 2.8.4
config file = /Users/dkimsey/.ansible.cfg
configured module search path = ['/Users/dkimsey/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /Users/dkimsey/.virtualenvs/ansible-2.8/lib/python3.7/site-packages/ansible
executable location = /Users/dkimsey/.virtualenvs/ansible-2.8/bin/ansible
python version = 3.7.3 (default, May 1 2019, 10:48:04) [Clang 10.0.0 (clang-1000.11.45.5)]
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
ANSIBLE_NOCOWS(/Users/dkimsey/.ansible.cfg) = True
ANSIBLE_PIPELINING(/Users/dkimsey/.ansible.cfg) = True
ANSIBLE_SSH_ARGS(/Users/dkimsey/.ansible.cfg) = -C -o ControlMaster=auto -o ControlPersist=300s -o ConnectTimeout=30
DEFAULT_BECOME(/Users/dkimsey/.ansible.cfg) = True
DIFF_ALWAYS(/Users/dkimsey/.ansible.cfg) = True
RETRY_FILES_ENABLED(/Users/dkimsey/.ansible.cfg) = False
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
OS X, Python 3.7
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
<!--- Paste example playbooks or commands between quotes below -->
```yaml
- hosts: all
tasks:
- name: Allow memcached to listen on tcp ports 10000 and 10112
seport:
ports:
- 10000
- 10112
proto: tcp
setype: memcache_port_t
state: present
```
<!--- HINT: You can paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
It should parse & apply correctly.
##### ACTUAL RESULTS
<!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) -->
It throws an exception, `AttributeError: 'int' object has no attribute 'split'`
<!--- Paste verbatim command output between quotes -->
```paste below
fatal: [localhost]: FAILED! => {"changed": false, "module_stderr": "Traceback (most recent call last):\n File \"<stdin>\", line 114, in <module>\n File \"<stdin>\", line 106, in _ansiballz_main\n File \"<stdin>\", line 49, in invoke_module\n File \"/tmp/ansible_seport_payload_EvYc5a/__main__.py\", line 307, in <module>\n File \"/tmp/ansible_seport_payload_EvYc5a/__main__.py\", line 297, in main\n File \"/tmp/ansible_seport_payload_EvYc5a/__main__.py\", line 206, in semanage_port_add\n File \"/tmp/ansible_seport_payload_EvYc5a/__main__.py\", line 159, in semanage_port_get_type\nAttributeError: 'int' object has no attribute 'split'\n", "module_stdout": "", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1}
```
```
Traceback (most recent call last):
File "<stdin>", line 114, in <module>
File "<stdin>", line 106, in _ansiballz_main
File "<stdin>", line 49, in invoke_module
File "/tmp/ansible_seport_payload_EvYc5a/__main__.py", line 307, in <module>
File "/tmp/ansible_seport_payload_EvYc5a/__main__.py", line 297, in main
File "/tmp/ansible_seport_payload_EvYc5a/__main__.py", line 206, in semanage_port_add
File "/tmp/ansible_seport_payload_EvYc5a/__main__.py", line 159, in semanage_port_get_type
AttributeError: 'int' object has no attribute 'split'
``` | https://github.com/ansible/ansible/issues/60968 | https://github.com/ansible/ansible/pull/65134 | 4a54873023c80b826e8cbcda28c44ce36fc97606 | 570c82f068d58b1e6ad9d2611bf647c3c82e6db0 | 2019-08-20T18:09:44Z | python | 2019-12-12T08:45:33Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 60,961 | ["changelogs/fragments/60961-docker_compose-fix-deprecation-warning.yml", "lib/ansible/modules/cloud/docker/docker_compose.py"] | docker_compose treats Docker deprecation notice as a failure | <!--- Verify first that your issue is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
The latest Docker release has a bug that causes it to spit out a spurious deprecation warning when you pull an image. https://github.com/moby/moby/issues/39701
Ansible's `docker_compose` module treats that warning as a fatal error even though the operation actually succeeds.
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
docker_compose
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
ansible 2.8.4
config file = /Users/koreth/work/terraform-configs/ansible/ansible.cfg
configured module search path = ['/Users/koreth/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /usr/local/Cellar/ansible/2.8.4/libexec/lib/python3.7/site-packages/ansible
executable location = /usr/local/bin/ansible
python version = 3.7.4 (default, Jul 9 2019, 18:13:23) [Clang 10.0.1 (clang-1001.0.46.4)]
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
ANSIBLE_PIPELINING(/Users/koreth/work/terraform-configs/ansible/ansible.cfg) = True
ANSIBLE_SSH_CONTROL_PATH(/Users/koreth/work/terraform-configs/ansible/ansible.cfg) = %(directory)s/%%C
CACHE_PLUGIN(/Users/koreth/work/terraform-configs/ansible/ansible.cfg) = jsonfile
CACHE_PLUGIN_CONNECTION(/Users/koreth/work/terraform-configs/ansible/ansible.cfg) = /tmp/ansible-facts.json
CACHE_PLUGIN_TIMEOUT(/Users/koreth/work/terraform-configs/ansible/ansible.cfg) = 86400
DEFAULT_FORKS(/Users/koreth/work/terraform-configs/ansible/ansible.cfg) = 100
DEFAULT_GATHERING(/Users/koreth/work/terraform-configs/ansible/ansible.cfg) = smart
DEFAULT_ROLES_PATH(/Users/koreth/work/terraform-configs/ansible/ansible.cfg) = ['/Users/koreth/work/terraform-configs/ansible/thirdparty', '/Users/koreth/work/terraform-configs/ansible/roles', '/Users/koreth/work/terraform-configs/roles']
DEFAULT_VAULT_PASSWORD_FILE(/Users/koreth/work/terraform-configs/ansible/ansible.cfg) = /Users/koreth/work/terraform-configs/ansible/.vault-password
DEPRECATION_WARNINGS(/Users/koreth/work/terraform-configs/ansible/ansible.cfg) = False
DISPLAY_SKIPPED_HOSTS(/Users/koreth/work/terraform-configs/ansible/ansible.cfg) = False
RETRY_FILES_ENABLED(/Users/koreth/work/terraform-configs/ansible/ansible.cfg) = False
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
Target OS is Ubuntu 18.04.1
Docker version 19.03.1, build 74b1e89
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
<!--- Paste example playbooks or commands between quotes below -->
```yaml
- hosts: vagrant-test
tasks:
- docker_compose:
project_name: test
pull: yes
definition:
registrator:
image: gliderlabs/registrator:v7
```
<!--- HINT: You can paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
Docker image is pulled, service is launched, and task succeeds.
##### ACTUAL RESULTS
<!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) -->
Docker image is pulled, service is launched, and task fails because of the unexpected warning message from Docker.
<!--- Paste verbatim command output between quotes -->
```paste below
TASK [docker_compose] *******************************************************************************
fatal: [vagrant-test]: FAILED! => {"changed": false, "module_stderr": "", "module_stdout": "v7: Pulling from gliderlabs/registrator\n[DEPRECATION NOTICE] registry v2 schema1 support will be removed in an upcoming release. Please contact admins of the docker.io registry NOW to avoid future disruption.\nDigest: sha256:0caaf84db8d645993964a0225c0485e7853135bf368393ce5a3a2c854379d476\nStatus: Image is up to date for gliderlabs/registrator:v7\n\n{\"services\": {\"registrator\": {\"test_registrator_1\": {\"cmd\": [], \"state\": {\"status\": \"running\", \"running\": true}, \"labels\": {\"com.docker.compose.service\": \"registrator\", \"com.docker.compose.config-hash\": \"5d06bcd558d0ce87526005a2d05a4c2b652d3952bdaeef9681d8552426863824\", \"com.docker.compose.project\": \"test\", \"com.docker.compose.version\": \"1.24.1\", \"com.docker.compose.oneoff\": \"False\", \"com.docker.compose.container-number\": \"1\"}, \"networks\": {\"bridge\": {\"macAddress\": \"02:42:ac:11:00:02\", \"globalIPv6PrefixLen\": 0, \"links\": null, \"IPPrefixLen\": 16, \"globalIPv6\": \"\", \"IPAddress\": \"172.17.0.2\", \"aliases\": []}}, \"image\": \"gliderlabs/registrator:v7\"}}}, \"invocation\": {\"module_args\": {\"project_src\": null, \"hostname_check\": false, \"recreate\": \"smart\", \"docker_host\": \"unix://var/run/docker.sock\", \"remove_images\": null, \"client_key\": null, \"scale\": null, \"nocache\": false, \"remove_volumes\": false, \"state\": \"present\", \"build\": false, \"client_cert\": null, \"api_version\": \"auto\", \"files\": null, \"project_name\": \"test\", \"ca_cert\": null, \"pull\": true, \"tls_hostname\": \"localhost\", \"dependencies\": true, \"services\": null, \"tls\": false, \"definition\": {\"registrator\": {\"image\": \"gliderlabs/registrator:v7\"}}, \"remove_orphans\": false, \"restarted\": false, \"ssl_version\": null, \"stopped\": false, \"timeout\": 10, \"debug\": false, \"validate_certs\": false}}, \"changed\": true, \"ansible_facts\": {\"registrator\": {\"test_registrator_1\": {\"cmd\": [], \"state\": {\"status\": \"running\", \"running\": true}, \"labels\": {\"com.docker.compose.service\": \"registrator\", \"com.docker.compose.config-hash\": \"5d06bcd558d0ce87526005a2d05a4c2b652d3952bdaeef9681d8552426863824\", \"com.docker.compose.project\": \"test\", \"com.docker.compose.version\": \"1.24.1\", \"com.docker.compose.oneoff\": \"False\", \"com.docker.compose.container-number\": \"1\"}, \"networks\": {\"bridge\": {\"macAddress\": \"02:42:ac:11:00:02\", \"globalIPv6PrefixLen\": 0, \"links\": null, \"IPPrefixLen\": 16, \"globalIPv6\": \"\", \"IPAddress\": \"172.17.0.2\", \"aliases\": []}}, \"image\": \"gliderlabs/registrator:v7\"}}}}\n", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 0}
```
| https://github.com/ansible/ansible/issues/60961 | https://github.com/ansible/ansible/pull/61650 | d5c8d325e43cdea45a2deccd47023ee86b072b43 | 0c73e47a42f69901ea892f9d0e58acb554f4e668 | 2019-08-20T16:37:00Z | python | 2019-09-04T17:34:05Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 60,921 | ["lib/ansible/modules/cloud/amazon/rds_instance.py", "test/integration/targets/rds_instance/tasks/test_modification.yml"] | rds_instance lack of MaxAllocatedStorage parameter |
##### SUMMARY
RDS services can auto-allocate storage. So you can start with the lowest ebs volume and don't care anymore about growing data in der database.
The boto3 parameter to activate this feature is `MaxAllocatedStorage` (integer)
> The upper limit to which Amazon RDS can automatically scale the storage of the DB instance.
##### ISSUE TYPE
- Feature Idea
##### COMPONENT NAME
rds_instance
| https://github.com/ansible/ansible/issues/60921 | https://github.com/ansible/ansible/pull/61008 | 628aa3a80810eb45cb61eff848f29cb48bb6de83 | 2fff40d409370a2e5cd95ae96cad6e260ea7fb6b | 2019-08-20T06:18:11Z | python | 2019-08-22T12:20:50Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 60,773 | ["changelogs/fragments/60805-aws_kms-ID-and-ARN-fixes.yml", "lib/ansible/modules/cloud/amazon/aws_kms.py", "test/integration/targets/aws_kms/tasks/main.yml"] | aws_kms fails with NotFoundException when working cross-account | ##### SUMMARY
If you pass aws_kms an existing key_id from another account (for example so you can set up a grant) it uses key['key_id'] in update_policy which effectively strips the account part of the ARN and results in a DescribeKey operation being called against the current account rather than the
```
NotFoundException: An error occurred (NotFoundException) when calling the DescribeKey operation: Key '...' does not exist
```
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
lib/ansible/modules/cloud/amazon/aws_kms.py
##### ANSIBLE VERSION
```
ansible 2.8.2
config file = /home/mchappel/.ansible.cfg
configured module search path = [u'/home/mchappel/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python2.7/site-packages/ansible
executable location = /usr/bin/ansible
python version = 2.7.5 (default, Jun 11 2019, 12:19:05) [GCC 4.8.5 20150623 (Red Hat 4.8.5-36)]
```
##### CONFIGURATION
```
DEFAULT_CALLBACK_WHITELIST(/home/mchappel/.ansible.cfg) = [u'timer', u'profile_tasks']
DEFAULT_VAULT_IDENTITY_LIST(/home/mchappel/.ansible.cfg) = [u'original@/home/mchappel/.ansible/secrets/original', u'ssl@/home/mchappel/.ansible/secrets/ssl', u'jenkins@/home/mchappel/.ansible/secrets/jenkins']
HOST_KEY_CHECKING(/home/mchappel/.ansible.cfg) = False
RETRY_FILES_ENABLED(/home/mchappel/.ansible.cfg) = False
```
##### OS / ENVIRONMENT
RHEL7
##### STEPS TO REPRODUCE
- Create a CMK in Account 1 and *share* it with Account 2
- Grant user from Account 2 permissions to access the CMK in Account 1
- Using User from Account 2 attempt to access the CMK
```
- aws_kms:
key_id: 'arn:aws:kms:us-west-2:XXX-Account-1-XXX:key/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX'
```
##### EXPECTED RESULTS
```
TASK [aws_kms] *******************************************************************************************************************************************************************************************************************************
Monday 19 August 2019 11:35:36 +0200 (0:00:00.051) 0:00:01.490 *********
ok: [mchappel]
```
##### ACTUAL RESULTS
```
TASK [aws_kms] *******************************************************************************************************************************************************************************************************************************
Monday 19 August 2019 10:49:37 +0200 (0:00:00.025) 0:00:01.284 *********
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: NotFoundException: An error occurred (NotFoundException) when calling the DescribeKey operation: Key 'arn:aws:kms:us-west-2:XXX-Account-2-XXX:key/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX' does not exist
fatal: [mchappel]: FAILED! => {"boto3_version": "1.4.6", "botocore_version": "1.6.0", "changed": false, "error": {"code": "NotFoundException", "message": "Key 'arn:aws:kms:us-west-2:XXX-Account-2-XXX:key/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX' does not exist"}, "msg": "Failed to obtain key metadata: An error occurred (NotFoundException) when calling the DescribeKey operation: Key 'arn:aws:kms:us-west-2:XXX-Account-2-XXX:key/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX' does not exist", "response_metadata": {"http_headers": {"cache-control": "no-cache, no-store, must-revalidate, private", "content-length": "139", "content-type": "application/x-amz-json-1.1", "date": "Mon, 19 Aug 2019 08:49:41 GMT", "expires": "0", "pragma": "no-cache", "x-amzn-requestid": "2c29ad8c-348c-4ef2-9260-8fb1f21407b1"}, "http_status_code": 400, "request_id": "2c29ad8c-348c-4ef2-9260-8fb1f21407b1", "retry_attempts": 0}}
```
##### ADDITIONAL DETAILS
@willthames
Again I have a fix (unable to create a test because the integration tests all expect to work with a single account...) will submit a MR once we've got your test fixes in and start merging.
| https://github.com/ansible/ansible/issues/60773 | https://github.com/ansible/ansible/pull/60805 | 4551965af168f9762d33409e4c06c1b88ce59999 | 5434bf74c646d0f61bf11b6a9c207d34547d0191 | 2019-08-19T10:06:01Z | python | 2019-08-23T23:56:45Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 60,750 | ["lib/ansible/plugins/doc_fragments/meraki.py"] | Does the module "meraki_vlan" work with Meraki China? | <!--- Verify first that your improvement is not already reported on GitHub -->
I had a search in Github, no related topic
<!--- Also test if the latest release and devel branch are affected too -->
The latest release doesn't work for us.
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
<!--- Explain the problem briefly below, add suggestions to wording or structure -->
We are truely interested in managing the Meraki by Ansible , but we run into some errors when the module meraki_vlan is executed.
Meraki China has the domain name "meraki.cn" while the global domain name is "meraki.com".We are wondering if the module "meraki_vlan" work with Meraki China? Please advise.
Really looking forward to see your feedback.
<!--- HINT: Did you know the documentation has an "Edit on GitHub" link on every page ? -->
Yes
##### ISSUE TYPE
- Documentation Report
##### COMPONENT NAME
<!--- Write the short name of the rst file, module, plugin, task or feature below, use your best guess if unsure -->
meraki_vlan
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
ansible 2.7.0
config file = /etc/ansible/ansible.cfg
configured module search path = [u'/root/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /usr/local/lib/python2.7/dist-packages/ansible
executable location = /usr/local/bin/ansible
python version = 2.7.12 (default, Dec 4 2017, 14:50:18) [GCC 5.4.0 20160609]
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
root@ubuntu:/usr/local/lib/python2.7/dist-packages# ansible-config dump --only-changed
ANSIBLE_SSH_ARGS(/etc/ansible/ansible.cfg) = -C -o ControlMaster=auto -o ControlPersist=30m
ANSIBLE_SSH_CONTROL_PATH(/etc/ansible/ansible.cfg) = ~/.ssh/ansible-%%r@%%h:%%p
HOST_KEY_CHECKING(/etc/ansible/ansible.cfg) = False
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. OS version, browser, etc. -->
##### ADDITIONAL INFORMATION
<!--- Describe how this improves the documentation, e.g. before/after situation or screenshots -->
<!--- HINT: You can paste gist.github.com links for larger files -->
| https://github.com/ansible/ansible/issues/60750 | https://github.com/ansible/ansible/pull/60967 | 32f264d50876a3f42909a77645d150f9609860b3 | 48a04fade419b1a491a372f6a1d3b5d6267fc905 | 2019-08-19T05:26:00Z | python | 2019-08-20T18:20:31Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 60,744 | ["changelogs/fragments/60805-aws_kms-ID-and-ARN-fixes.yml", "lib/ansible/modules/cloud/amazon/aws_kms.py", "test/integration/targets/aws_kms/tasks/main.yml"] | aws_kms throws exception when only Key ID is passed | ##### SUMMARY
If you pass aws_kms an existing key_id and no alias, it throws exceptions
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
lib/ansible/modules/cloud/amazon/aws_kms.py
##### ANSIBLE VERSION
```
ansible 2.8.2
config file = /home/mchappel/.ansible.cfg
configured module search path = [u'/home/mchappel/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python2.7/site-packages/ansible
executable location = /usr/bin/ansible
python version = 2.7.5 (default, Jun 11 2019, 12:19:05) [GCC 4.8.5 20150623 (Red Hat 4.8.5-36)]
```
##### CONFIGURATION
```
DEFAULT_CALLBACK_WHITELIST(/home/mchappel/.ansible.cfg) = [u'timer', u'profile_tasks']
DEFAULT_VAULT_IDENTITY_LIST(/home/mchappel/.ansible.cfg) = [u'original@/home/mchappel/.ansible/secrets/original', u'ssl@/home/mchappel/.ansible/secrets/ssl', u'jenkins@/home/mchappel/.ansible/secrets/jenkins']
HOST_KEY_CHECKING(/home/mchappel/.ansible.cfg) = False
RETRY_FILES_ENABLED(/home/mchappel/.ansible.cfg) = False
```
##### OS / ENVIRONMENT
RHEL7
##### STEPS TO REPRODUCE
```
- name: Update Policy on key to match AWS Console generate policy
aws_kms:
key_id: '{{ new_key["keys"][0]["key_id"] }}'
policy: "{{ lookup('template', 'console-policy.j2') | to_json }}"
register: kms_policy_changed
```
##### EXPECTED RESULTS
Key successfully updated
##### ACTUAL RESULTS
Exception. (There's actually a couple of places that need updating)
##### ADDITIONAL DETAILS
@willthames
https://github.com/tremble/ansible/tree/aws_kms_keyid_only contains updated tests and a fix. I'll submit a PR once we know what order everything's likely to get merged in. Side effect of the change, aws_kms is substantially faster, as a result I had to more the iam_role creation in the test suite. | https://github.com/ansible/ansible/issues/60744 | https://github.com/ansible/ansible/pull/60805 | 4551965af168f9762d33409e4c06c1b88ce59999 | 5434bf74c646d0f61bf11b6a9c207d34547d0191 | 2019-08-18T12:32:16Z | python | 2019-08-23T23:56:45Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 60,731 | ["docs/docsite/rst/user_guide/playbooks_delegation.rst", "docs/docsite/rst/user_guide/playbooks_error_handling.rst"] | any_errors_fatal does not work | ##### SUMMARY
Even in the simplest playbook, the `any_errors_fatal: true` construct does not work
##### ISSUE TYPE
- Documentation Report
##### COMPONENT NAME
any_errors_fatal
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
ansible 2.8.3
config file = None
configured module search path = ['/Users/tennis.smith/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /usr/local/Cellar/ansible/2.8.3/libexec/lib/python3.7/site-packages/ansible
executable location = /usr/local/bin/ansible
python version = 3.7.4 (default, Jul 9 2019, 18:13:23) [Clang 10.0.1 (clang-1001.0.46.4)]
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
RETRY_FILES_ENABLED(env: ANSIBLE_RETRY_FILES_ENABLED) = False
```
##### OS / ENVIRONMENT
Any
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
```
ansible-playbook -i <hosts> ./create_vlan.yml --extra-vars '@vlan_103.yml'
```
<!--- Paste example playbooks or commands between quotes below -->
VLAN config file:
```yaml
---
vlan_number: 103
vlan_name: test_103
ports:
n9kv1:
- Ethernet1/88
- Ethernet1/89
- Ethernet1/90
n9kv2:
- Ethernet1/99
```
Playbook:
```yaml
- name: vlan testing
hosts: switches
any_errors_fatal: true
connection: local
gather_facts: no
tasks:
- name: Build VLAN
nxos_vlan:
vlan_id: "{{ vlan_number }}"
name: "{{ vlan_name }}"
state: present
interfaces: "{{ ports[inventory_hostname] }}"
when: inventory_hostname in ports
```
##### EXPECTED RESULTS
The playbook should fail on the first error found.
##### ACTUAL RESULTS
There are 2 errors in the output and the playbook continues to the end. It should have aborted on the first error. The error itself was reported in a separate issue (#60729).
<!--- Paste verbatim command output between quotes -->
```paste below
PLAY [vlan testing] ******************************************************************************************************************
TASK [Build VLAN] ********************************************************************************************************************
skipping: [n7ksw1]
skipping: [n7ksw2]
fatal: [n95ksw2]: FAILED! => {"ansible_facts": {"discovered_interpreter_python": "/usr/bin/python"}, "changed": false, "msg": "switchport\r\r\n ^\r\n% Invalid command at '^' marker.\r\n\rJER-LAB-95KSW2(config-if)# "}
fatal: [n95ksw1]: FAILED! => {"ansible_facts": {"discovered_interpreter_python": "/usr/bin/python"}, "changed": false, "msg": "switchport\r\r\n ^\r\n% Invalid command at '^' marker.\r\n\rJER-LAB-N95KSW1(config-if)# "}
NO MORE HOSTS LEFT *******************************************************************************************************************
PLAY RECAP ***************************************************************************************************************************
n7ksw1 : ok=0 changed=0 unreachable=0 failed=0 skipped=1 rescued=0 ignored=0
n7ksw2 : ok=0 changed=0 unreachable=0 failed=0 skipped=1 rescued=0 ignored=0
n95ksw1 : ok=0 changed=0 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0
n95ksw2 : ok=0 changed=0 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0
```
| https://github.com/ansible/ansible/issues/60731 | https://github.com/ansible/ansible/pull/62029 | 0e72cbd45114dff22dcd464529ec9918d9ecaf39 | 09f1c286e00828294802623da4a6b4880ec279a5 | 2019-08-17T14:36:21Z | python | 2019-09-12T20:15:02Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 60,707 | ["lib/ansible/modules/packaging/os/package_facts.py"] | package_facts requires python-apt on Debian systems in ansible 2.8.3 | ##### SUMMARY
The document for package_facts does not specify a requirement of python-apt being in an installed state on the system of which the module `package_facts` is going to collect package related data. While this may not cause any issue for EL based systems or any other - package_facts will return an error when used on any Debian based systems where python-apt package is not already in an installed state.
##### ISSUE TYPE
- Documentation Report
##### COMPONENT NAME
package_facts
##### ANSIBLE VERSION
```
2.8.3
```
##### OS / ENVIRONMENT
* Ubuntu 18.04
* Ubuntu 16.04
* Debian 8
* Debian 9
* Debian 10
##### STEPS TO REPRODUCE
On any debian based system, ensure that python-apt package is not available to test it.
```shell
sudo apt-get remove python-apt
```
Then run the following playbook on an ansible controller node to test locally.
```yaml
name: Playbook to test package_facts module locally on any Debian based system.
hosts: localhost
become: yes
connection: local
gather_facts: yes
tasks:
- name: Gather package facts on Debian based systems
package_facts:
manager: auto
when: ansible_os_family == "Debian"
```
##### EXPECTED RESULTS
```yaml
$ ansible-playbook package.yml
PLAY [Playbook to test package_facts module locally on any Debian based system.] *******
TASK [Gathering Facts] *****************************************************************
ok: [localhost]
TASK [Gather package facts on Debian based systems] ************************************
ok: [localhost]
PLAY RECAP *****************************************************************************
localhost : ok=2 changed=0 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0
```
##### ACTUAL RESULTS
```yaml
$ ansible-playbook package.yml
PLAY [Playbook to test package_facts module locally on any Debian based system.] *******
TASK [Gathering Facts] *****************************************************************
ok: [localhost]
TASK [Gather package facts on Debian based systems] ************************************
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Could not detect a supported package manager from the following list: ['portage', 'rpm', 'pkg', 'apt']"}
PLAY RECAP *****************************************************************************
localhost : ok=1 changed=0 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0
```
##### Temporary workaround:
To install `python-apt` package on any Debian based systems where package_facts module is going to be used for.
##### Recommendation:
To either remove dependency on python-apt for Debian based systems from package_facts module or to specify python-apt requirement (for Debain based systems) in package_facts documentation.
| https://github.com/ansible/ansible/issues/60707 | https://github.com/ansible/ansible/pull/60999 | 35d457a14f736b99692827ab21306629f9c385ff | cf291f272d23a1ee4c1e6401caa7098ed5857895 | 2019-08-16T20:17:59Z | python | 2019-08-21T18:22:10Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 60,685 | ["lib/ansible/module_utils/network/ios/config/interfaces/interfaces.py", "lib/ansible/module_utils/network/ios/utils/utils.py", "lib/ansible/modules/network/ios/ios_interfaces.py"] | Unit tests for ios_interfaces is failing | <!--- Verify first that your issue is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
<!--- Explain the problem briefly below -->
Unit tests for ios_interfaces is failing, with import error
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
<!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure -->
ios_interfaces
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
devel
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
macos
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
<!--- Paste example playbooks or commands between quotes below -->
```yaml
```
<!--- HINT: You can paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
Unit tests for `ios_interfaces` should pass w/o any issue/failure
##### ACTUAL RESULTS
<!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) -->
Unit tests are failing with error: `ImportError: cannot import name 'dict_diff' from 'ansible.module_utils.network.ios.utils.utils'`
<!--- Paste verbatim command output between quotes -->
```paste below
```
| https://github.com/ansible/ansible/issues/60685 | https://github.com/ansible/ansible/pull/60687 | 064cd63f3d1c70019ca10a5eba75212ee9705c16 | 585bfead75085bc73aec1f3d35320b53e083922d | 2019-08-16T12:42:27Z | python | 2019-08-16T13:55:28Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 60,674 | ["lib/ansible/plugins/cliconf/eric_eccli.py"] | cli_command newline argument issue | <!--- Verify first that your issue is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
<!--- Explain the problem briefly below -->
cli_command returns error regarding unexpected newline argument on command prompt
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
<!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure -->
cli_command
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
ansible 2.9.0.dev0
config file = /etc/ansible/ansible.cfg
configured module search path = [u'/home/ansibleUser/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /mnt/c/ansible/repo/devel/ansible/lib/ansible
executable location = /mnt/c/ansible/repo/devel/ansible/bin/ansible
python version = 2.7.15+ (default, Nov 27 2018, 23:36:35) [GCC 7.3.0]
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
HOST_KEY_CHECKING(/etc/ansible/ansible.cfg) = False
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
```
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.2 LTS"
NAME="Ubuntu"
VERSION="18.04.2 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.2 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
```
Network device: Ericsson Router 6672 and 6675
IPOS-v19.1.1.803.107-Release
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
```
- name: save configuration to flash memory
cli_command:
command: save configuration
prompt:
- '(y/n)'
answer:
- 'y'
```
<!--- HINT: You can paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
The task should answer the prompt correctly with "y" and continue
```
ok: [10.68.80.242] => {
"changed": false,
"invocation": {
"module_args": {
"answer": [
"y"
],
"check_all": false,
"command": "save configuration",
"newline": true,
"prompt": [
"(y/n)"
],
"sendonly": false
}
},
"stdout": "Save to file: /flash/deviceConfig.cfg\nTarget file exists, overwrite? (y/n) y",
"stdout_lines": [
"Save to file: /flash/decviceConfig.cfg",
"Target file exists, overwrite? (y/n) y"
]
}
ok: [10.68.80.121] => {
"changed": false,
"invocation": {
"module_args": {
"answer": [
"y"
],
"check_all": false,
"command": "save configuration",
"newline": true,
"prompt": [
"(y/n)"
],
"sendonly": false
}
},
"stdout": "Save to file: /flash/deviceConfig.cfg\nTarget file exists, overwrite? (y/n) y",
"stdout_lines": [
"Save to file: /flash/deviceConfig.cfg",
"Target file exists, overwrite? (y/n) y"
]
}
```
##### ACTUAL RESULTS
<!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) -->
```
<10.68.80.121> attempting to start connection
<10.68.80.121> using connection plugin network_cli
<10.68.80.242> attempting to start connection
<10.68.80.242> using connection plugin network_cli
<10.68.80.121> found existing local domain socket, using it!
<10.68.80.121> updating play_context for connection
<10.68.80.121>
<10.68.80.121> local domain socket path is /home/ansibleUser/.ansible/pc/7ebc00b4de
<10.68.80.242> found existing local domain socket, using it!
<10.68.80.242> updating play_context for connection
<10.68.80.242>
<10.68.80.242> local domain socket path is /home/ansibleUser/.ansible/pc/4429d07464
<10.68.80.121> ESTABLISH LOCAL CONNECTION FOR USER: ansibleUser
<10.68.80.121> EXEC /bin/sh -c '( umask 77 && mkdir -p "` echo /home/ansibleUser/.ansible/tmp/ansible-local-13435c4s0G5/ansible-tmp-1565946129.18-225284847083129 `" && echo ansible-tmp-1565946129.18-225284847083129="` echo /home/ansibleUser/.ansible/tmp/ansible-local-13435c4s0G5/ansible-tmp-1565946129.18-225284847083129 `" ) && sleep 0'
<10.68.80.242> ESTABLISH LOCAL CONNECTION FOR USER: ansibleUser
<10.68.80.242> EXEC /bin/sh -c '( umask 77 && mkdir -p "` echo /home/ansibleUser/.ansible/tmp/ansible-local-13435c4s0G5/ansible-tmp-1565946129.19-185648273166358 `" && echo ansible-tmp-1565946129.19-185648273166358="` echo /home/ansibleUser/.ansible/tmp/ansible-local-13435c4s0G5/ansible-tmp-1565946129.19-185648273166358 `" ) && sleep 0'
Using module file /mnt/c/ansible/repo/devel/ansible/lib/ansible/modules/network/cli/cli_command.py
Using module file /mnt/c/ansible/repo/devel/ansible/lib/ansible/modules/network/cli/cli_command.py
<10.68.80.242> PUT /home/ansibleUser/.ansible/tmp/ansible-local-13435c4s0G5/tmpsaD_6r TO /home/ansibleUser/.ansible/tmp/ansible-local-13435c4s0G5/ansible-tmp-1565946129.19-185648273166358/AnsiballZ_cli_command.py
<10.68.80.121> PUT /home/ansibleUser/.ansible/tmp/ansible-local-13435c4s0G5/tmpwf0Dac TO /home/ansibleUser/.ansible/tmp/ansible-local-13435c4s0G5/ansible-tmp-1565946129.18-225284847083129/AnsiballZ_cli_command.py
<10.68.80.242> EXEC /bin/sh -c 'chmod u+x /home/ansibleUser/.ansible/tmp/ansible-local-13435c4s0G5/ansible-tmp-1565946129.19-185648273166358/ /home/ansibleUser/.ansible/tmp/ansible-local-13435c4s0G5/ansible-tmp-1565946129.19-185648273166358/AnsiballZ_cli_command.py && sleep 0'
<10.68.80.121> EXEC /bin/sh -c 'chmod u+x /home/ansibleUser/.ansible/tmp/ansible-local-13435c4s0G5/ansible-tmp-1565946129.18-225284847083129/ /home/ansibleUser/.ansible/tmp/ansible-local-13435c4s0G5/ansible-tmp-1565946129.18-225284847083129/AnsiballZ_cli_command.py && sleep 0'
<10.68.80.242> EXEC /bin/sh -c '/usr/bin/python /home/ansibleUser/.ansible/tmp/ansible-local-13435c4s0G5/ansible-tmp-1565946129.19-185648273166358/AnsiballZ_cli_command.py && sleep 0'
<10.68.80.121> EXEC /bin/sh -c '/usr/bin/python /home/ansibleUser/.ansible/tmp/ansible-local-13435c4s0G5/ansible-tmp-1565946129.18-225284847083129/AnsiballZ_cli_command.py && sleep 0'
<10.68.80.242> EXEC /bin/sh -c 'rm -f -r /home/ansibleUser/.ansible/tmp/ansible-local-13435c4s0G5/ansible-tmp-1565946129.19-185648273166358/ > /dev/null 2>&1 && sleep 0'
<10.68.80.121> EXEC /bin/sh -c 'rm -f -r /home/ansibleUser/.ansible/tmp/ansible-local-13435c4s0G5/ansible-tmp-1565946129.18-225284847083129/ > /dev/null 2>&1 && sleep 0'
The full traceback is:
WARNING: The below traceback may *not* be related to the actual failure.
File "/tmp/ansible_cli_command_payload_Z9SLy8/__main__.py", line 167, in main
response = connection.get(**module.params)
File "/tmp/ansible_cli_command_payload_Z9SLy8/ansible_cli_command_payload.zip/ansible/module_utils/connection.py", line 186, in __rpc__
raise ConnectionError(to_text(msg, errors='surrogate_then_replace'), code=code)
fatal: [10.68.80.121]: FAILED! => {
"changed": false,
"invocation": {
"module_args": {
"answer": [
"y"
],
"check_all": false,
"command": "save configuration",
"newline": true,
"prompt": [
"(y/n)"
],
"sendonly": false
}
},
"msg": "get() got an unexpected keyword argument 'newline'"
}
The full traceback is:
WARNING: The below traceback may *not* be related to the actual failure.
File "/tmp/ansible_cli_command_payload_nNw0EE/__main__.py", line 167, in main
response = connection.get(**module.params)
File "/tmp/ansible_cli_command_payload_nNw0EE/ansible_cli_command_payload.zip/ansible/module_utils/connection.py", line 186, in __rpc__
raise ConnectionError(to_text(msg, errors='surrogate_then_replace'), code=code)
fatal: [10.68.80.242]: FAILED! => {
"changed": false,
"invocation": {
"module_args": {
"answer": [
"y"
],
"check_all": false,
"command": "save configuration",
"newline": true,
"prompt": [
"(y/n)"
],
"sendonly": false
}
},
"msg": "get() got an unexpected keyword argument 'newline'"
}
```
If newline parameter in lib/ansible/modules/network/cli/cli_command.py (line: 147)
is commented out the task succeeds with the expected results.
Different argument options in playbook have been tried, nothing resulted in a positive outcome.
| https://github.com/ansible/ansible/issues/60674 | https://github.com/ansible/ansible/pull/61507 | aa58bb9d437021010a63bf86f1d93bda08f48a47 | d7845da326e3d0cf74ff813a0e8b84b4137d185d | 2019-08-16T09:11:25Z | python | 2019-08-29T05:02:38Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 60,627 | ["lib/ansible/modules/network/junos/junos_user.py"] | junos_user encrypted_password should be set no_log | <!--- Verify first that your issue is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
<!--- Explain the problem briefly below -->
junos_user encrypted_password option is no set no_log.
So, I get "[WARNING]: Module did not set no_log for encrypted_password"
It be set no_log.
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
<!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure -->
junos_user module
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
$ ansible --version
ansible 2.8.3
config file = /vagrant/test/ansible.cfg
configured module search path = ['/home/vagrant/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /home/vagrant/ansible2830/lib64/python3.6/site-packages/ansible
executable location = /home/vagrant/ansible2830/bin/ansible
python version = 3.6.8 (default, May 2 2019, 20:40:44) [GCC 4.8.5 20150623 (Red Hat 4.8.5-36)]```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
$ ansible-config dump --only-changed
HOST_KEY_CHECKING(/vagrant/test/ansible.cfg) = False
RETRY_FILES_ENABLED(/vagrant/test/ansible.cfg) = False
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
```
$ cat /etc/redhat-release
CentOS Linux release 7.5.1804 (Core)
$ uname -a
Linux centos7 3.10.0-862.14.4.el7.x86_64 #1 SMP Wed Sep 26 15:12:11 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
```
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
$ ansible-playbook -i inventory/inventory.ini junos_user.yml
<!--- Paste example playbooks or commands between quotes below -->
- playbook
```yaml
---
- hosts: junos
gather_facts: no
tasks:
- name: set junos user
junos_user:
name: testuser
sshkey: "{{ lookup('file', '/home/vagrant/user_keys/admin01_id_rsa.pub') }}"
role: super-user
```
<!--- HINT: You can paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
```
$ ansible-playbook -i inventory/inventory.ini network_set_junos_user.yml
PLAY [junos] ******************************************************************************************************
TASK [set junos user] *********************************************************************************************
[WARNING]: Platform linux on host junos01 is using the discovered Python interpreter at /usr/bin/python, but
future installation of another Python interpreter could change this. See
https://docs.ansible.com/ansible/2.8/reference_appendices/interpreter_discovery.html for more information.
changed: [junos01]
PLAY RECAP ********************************************************************************************************
junos01 : ok=1 changed=1 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0
```
##### ACTUAL RESULTS
<!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) -->
<!--- Paste verbatim command output between quotes -->
```paste below
(ansible2830) [vagrant@centos7 sec5]$ ansible-playbook -i inventory/inventory.ini network_set_junos_user.yml
PLAY [junos] ******************************************************************************************************
TASK [set junos user] *********************************************************************************************
[WARNING]: Module did not set no_log for encrypted_password
[WARNING]: Platform linux on host junos01 is using the discovered Python interpreter at /usr/bin/python, but
future installation of another Python interpreter could change this. See
https://docs.ansible.com/ansible/2.8/reference_appendices/interpreter_discovery.html for more information.
changed: [junos01]
PLAY RECAP ********************************************************************************************************
junos01 : ok=1 changed=1 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0
```
| https://github.com/ansible/ansible/issues/60627 | https://github.com/ansible/ansible/pull/62184 | cd4882e2297e78e46b676663d9c899148a16cc4f | 4e6270750a748ae854481e157821f51eda36ded0 | 2019-08-15T09:20:47Z | python | 2019-09-12T10:38:40Z |
closed | ansible/ansible | https://github.com/ansible/ansible | 60,605 | ["lib/ansible/modules/cloud/docker/docker_image_info.py"] | docker_image_info does not pull image automatically | <!--- Verify first that your issue is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
<!--- Explain the problem briefly below -->
When using ~~docker_container_info~~ docker_image_info - if the image has not been pulled previously, it doesn't return anything (empty images) - although the run is successful.
It returns "images: []"
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
<!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure -->
docker_image_info
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
ansible 2.8.3
config file = /etc/ansible/ansible.cfg
configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /usr/local/lib/python3.6/site-packages/ansible
executable location = /usr/local/bin/ansible
python version = 3.6.8 (default, Apr 25 2019, 21:02:35) [GCC 4.8.5 20150623 (Red Hat 4.8.5-36)]
```
##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
empty
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
CentOS 7.6
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
Run the following playbook (without first pulling the image) - it will return images: [], but after pulling the image either by docker pull or or docker_container module - it works.
<!--- Paste example playbooks or commands between quotes below -->
```yaml
---
- hosts: localhost
tasks:
- name: Fetch info
docker_image_info:
name: kolla/ubuntu-source-fluentd:master
register: fluentd_info
- name: Print info
debug:
var: fluentd_info
```
<!--- HINT: You can paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
If Docker image is not known to Docker engine - it should automatically pull the image.
Of course the output should be all Docker image info - not empty images: []
At least if this is correct behaviour - it should at least fail printing out that the Docker image is unknown/unpulled/anything.
##### ACTUAL RESULTS
<!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) -->
<!--- Paste verbatim command output between quotes -->
```paste below
TASK [common : Fetch fluentd image labels] *************************************
task path: /home/zuul/src/opendev.org/openstack/kolla-ansible/ansible/roles/common/tasks/config.yml:15
Using module file /usr/lib/python2.7/site-packages/ansible/modules/cloud/docker/docker_image_facts.py
<23.253.156.234> ESTABLISH SSH CONNECTION FOR USER: kolla
<23.253.156.234> SSH: EXEC ssh -C -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o 'IdentityFile="/home/zuul/.ssh/id_rsa_kolla"' -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=kolla -o ConnectTimeout=10 -o ControlPath=/home/zuul/.ansible/cp/32d0df4699 23.253.156.234 '/bin/sh -c '"'"'echo ~kolla && sleep 0'"'"''
<23.253.156.234> (0, '/home/kolla\n', '')
<23.253.156.234> ESTABLISH SSH CONNECTION FOR USER: kolla
<23.253.156.234> SSH: EXEC ssh -C -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o 'IdentityFile="/home/zuul/.ssh/id_rsa_kolla"' -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=kolla -o ConnectTimeout=10 -o ControlPath=/home/zuul/.ansible/cp/32d0df4699 23.253.156.234 '/bin/sh -c '"'"'( umask 77 && mkdir -p "` echo /home/kolla/.ansible/tmp/ansible-tmp-1565804195.42-162435853764977 `" && echo ansible-tmp-1565804195.42-162435853764977="` echo /home/kolla/.ansible/tmp/ansible-tmp-1565804195.42-162435853764977 `" ) && sleep 0'"'"''
<23.253.156.234> (0, 'ansible-tmp-1565804195.42-162435853764977=/home/kolla/.ansible/tmp/ansible-tmp-1565804195.42-162435853764977\n', '')
<23.253.156.234> PUT /home/zuul/.ansible/tmp/ansible-local-25260JN6G05/tmpWgzb8R TO /home/kolla/.ansible/tmp/ansible-tmp-1565804195.42-162435853764977/docker_image_facts.py
<23.253.156.234> SSH: EXEC sftp -b - -C -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o 'IdentityFile="/home/zuul/.ssh/id_rsa_kolla"' -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=kolla -o ConnectTimeout=10 -o ControlPath=/home/zuul/.ansible/cp/32d0df4699 '[23.253.156.234]'
<23.253.156.234> (0, 'sftp> put /home/zuul/.ansible/tmp/ansible-local-25260JN6G05/tmpWgzb8R /home/kolla/.ansible/tmp/ansible-tmp-1565804195.42-162435853764977/docker_image_facts.py\n', '')
<23.253.156.234> ESTABLISH SSH CONNECTION FOR USER: kolla
<23.253.156.234> SSH: EXEC ssh -C -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o 'IdentityFile="/home/zuul/.ssh/id_rsa_kolla"' -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=kolla -o ConnectTimeout=10 -o ControlPath=/home/zuul/.ansible/cp/32d0df4699 23.253.156.234 '/bin/sh -c '"'"'chmod u+x /home/kolla/.ansible/tmp/ansible-tmp-1565804195.42-162435853764977/ /home/kolla/.ansible/tmp/ansible-tmp-1565804195.42-162435853764977/docker_image_facts.py && sleep 0'"'"''
<23.253.156.234> (0, '', '')
<23.253.156.234> ESTABLISH SSH CONNECTION FOR USER: kolla
<23.253.156.234> SSH: EXEC ssh -C -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o 'IdentityFile="/home/zuul/.ssh/id_rsa_kolla"' -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=kolla -o ConnectTimeout=10 -o ControlPath=/home/zuul/.ansible/cp/32d0df4699 -tt 23.253.156.234 '/bin/sh -c '"'"'/usr/bin/python /home/kolla/.ansible/tmp/ansible-tmp-1565804195.42-162435853764977/docker_image_facts.py && sleep 0'"'"''
<23.253.156.234> (0, '\r\n{"images": [], "invocation": {"module_args": {"filter_logger": false, "tls": null, "cacert_path": null, "name": ["10.208.193.113:4000/lokolla/centos-source-fluentd:change_676413"], "ssl_version": null, "tls_hostname": null, "docker_host": null, "tls_verify": null, "key_path": null, "timeout": null, "debug": false, "cert_path": null, "api_version": null}}, "changed": false}\r\n', 'Shared connection to 23.253.156.234 closed.\r\n')
<23.253.156.234> ESTABLISH SSH CONNECTION FOR USER: kolla
<23.253.156.234> SSH: EXEC ssh -C -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o 'IdentityFile="/home/zuul/.ssh/id_rsa_kolla"' -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=kolla -o ConnectTimeout=10 -o ControlPath=/home/zuul/.ansible/cp/32d0df4699 23.253.156.234 '/bin/sh -c '"'"'rm -f -r /home/kolla/.ansible/tmp/ansible-tmp-1565804195.42-162435853764977/ > /dev/null 2>&1 && sleep 0'"'"''
<23.253.156.234> (0, '', '')
ok: [primary] => {
"changed": false,
"images": [],
"invocation": {
"module_args": {
"api_version": null,
"cacert_path": null,
"cert_path": null,
"debug": false,
"docker_host": null,
"filter_logger": false,
"key_path": null,
"name": [
"10.208.193.113:4000/lokolla/centos-source-fluentd:change_676413"
],
"ssl_version": null,
"timeout": null,
"tls": null,
"tls_hostname": null,
"tls_verify": null
}
}
}
```
| https://github.com/ansible/ansible/issues/60605 | https://github.com/ansible/ansible/pull/60622 | 555b8413a1fafaa15b38b715ba32ad7d22500350 | 7a9e865a235eb35c61fd2cb82b446b6f4ce5d18a | 2019-08-14T20:09:49Z | python | 2019-08-19T07:21:50Z |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.