Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

win_dns_client: Fix to compare ordering of resolver IP Addresses #34656

Merged
merged 1 commit into from
Jan 11, 2018

Conversation

chriskarel
Copy link
Contributor

SUMMARY

Fix for bug #34651

This change forces the module to consider the ordering of DNS entries when determining whether a change is needed. Previously, re-arranging the order of DNS resolvers was not detected as different, and therefore not changed.

ISSUE TYPE
  • Bugfix Pull Request
COMPONENT NAME

win_dns_clinet

ANSIBLE VERSION
ansible 2.4.2.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/lib/python2.7/site-packages/ansible
  executable location = /bin/ansible
  python version = 2.7.5 (default, May 29 2017, 20:42:36) [GCC 4.8.5 20150623 (Red Hat 4.8.5-11)]

ADDITIONAL INFORMATION

Adding "-SyncWindow 0" flag to the Compare-Object call used to determine if the existing and proposed IP address lists are the same. This makes the array comparison mark changes in order as a difference.

Adding "-SyncWindow 0" flag to the Compare-Object call used to determine if the existing and proposed IP address lists are the same.  This makes the array comparison mark changes in order as a difference.

Fix for bug ansible#34651
@ansibot
Copy link
Contributor

ansibot commented Jan 9, 2018

@ansibot ansibot added affects_2.5 This issue/PR affects Ansible v2.5 bugfix_pull_request core_review In order to be merged, this PR must follow the core review workflow. module This issue/PR relates to a module. needs_triage Needs a first human triage before being processed. support:core This issue/PR relates to code supported by the Ansible Engineering Team. windows Windows community labels Jan 9, 2018
@jborean93 jborean93 removed the needs_triage Needs a first human triage before being processed. label Jan 11, 2018
@jborean93
Copy link
Contributor

Looks good @chriskarel, thanks for the PR

@abadger
Copy link
Contributor

abadger commented Jan 15, 2018

Cherry-picked to stable-2.4 for the 2.4.3rc2 release.

abadger pushed a commit that referenced this pull request Jan 15, 2018
Adding "-SyncWindow 0" flag to the Compare-Object call used to determine if the existing and proposed IP address lists are the same.  This makes the array comparison mark changes in order as a difference.

Fix for bug #34651

(cherry picked from commit bb9dcb0)
@abadger abadger moved this from Nice to have to Done in 2.4.3 in 2.4.x Blocker List Jan 15, 2018
@ansibot ansibot added bug This issue/PR relates to a bug. and removed bugfix_pull_request labels Mar 6, 2018
@ansible ansible locked and limited conversation to collaborators Apr 26, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
affects_2.5 This issue/PR affects Ansible v2.5 bug This issue/PR relates to a bug. core_review In order to be merged, this PR must follow the core review workflow. module This issue/PR relates to a module. support:core This issue/PR relates to code supported by the Ansible Engineering Team. windows Windows community
Projects
No open projects
2.4.x Blocker List
Done in 2.4.3
Development

Successfully merging this pull request may close these issues.

None yet

4 participants