New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ansible Reports Validate Not Supported by Netconf Server when Enabled in Netconf #119
Comments
@jamesmarshall24 Please check if the linked PR on |
@jamesmarshall24 @ganeshrn Yes, this has resolved the issue. Thank you! |
@harrytruman Thanks for the confirmation. PR merged to |
This was referenced Aug 15, 2020
netbsd-srcmastr
pushed a commit
to NetBSD/pkgsrc
that referenced
this issue
Sep 8, 2020
v2.9.13 ======= Minor Changes ------------- - Updated network integration auth timeout to 90 secs. - ansible-test - Remove ``pytest < 6.0.0`` constraint for managed installations on Python 3.x now that pytest 6 is supported. - known_hosts - fix reference to non-existent parameter in example (ansible/ansible#71417) Security Fixes -------------- - The fix for CVE-2020-1736 has been reverted. Users are encouraged to specify a ``mode`` parameter in their file-based tasks when the files being manipulated contain sensitive data. - dnf - Previously, regardless of the ``disable_gpg_check`` option, packages were not GPG validated. They are now. (CVE-2020-14365) Bugfixes -------- - Confirmed commit fails with TypeError in IOS XR netconf plugin (ansible-collections/cisco.iosxr#74) - Fix an exit code for a non-failing playbook (ansible/ansible#71306) - Fix execution of the meta tasks 'clear_facts', 'clear_host_errors', 'end_play', 'end_host', and 'reset_connection' when the CLI flag '--flush-cache' is provided. - Fix statistics reporting when rescue block contains another block (issue ansible/ansible#61253). - Fixed Ansible reporting validate not supported by netconf server when enabled in netconf - (ansible-collections/ansible.netcommon#119). - TOML inventory - Ensure we register dump functions for ``AnsibleUnsafe`` to support dumping unsafe values. Note that the TOML format has no functionality to mark that the data is unsafe for re-consumption. (ansible/ansible#71307) - ansible-test units - fixed collection location code to work under pytest >= 6.0.0 - aws_acm_info - fix `KeyError` failure when retrieving keys with a `Failed` status (ansible-collections/community.aws#198) - cron - cron file should not be empty after adding var (ansible/ansible#71207) - mongodb_replicaset - fixes authentication to determine replicaset name (ansible-collections/community.mongodb#136). - powershell - fix escaping of strings that broken modules like fetch when dealing with special chars - ansible/ansible#62781 - powershell - fix the CLIXML parser when it contains nested CLIXML objects - ansible/ansible#69550 - psrp - Use native PSRP mechanism when copying files to support custom endpoints - setup - Add a null check for ``Win32_Bios.ReleaseData`` to avoid a failure when that value is not set - ansible/ansible#69736 - strftime filter - Input epoch is allowed to be a float (ansible/ansible#71257) - systemd - fixed chroot usage on new versions of systemd, that broke because of upstream changes in systemctl output - systemd - made the systemd module work correctly when the SYSTEMD_OFFLINE environment variable is set - zabbix_host - fixed inventory_mode key error, which occurs with Zabbix 4.4.1 or more (ansible/ansible#65304). - zabbix_proxy - fixed support for Zabbix 5.0
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
SUMMARY
Although validate is enabled in netconf, Ansible reports it is unable to validate
ISSUE TYPE
COMPONENT NAME
ansible.netcommon.netconf_config
ANSIBLE VERSION
OS / ENVIRONMENT
netconf version 1.0 and 1.1
STEPS TO REPRODUCE
EXPECTED RESULTS
netconf_config allows validate
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: