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

Infoblox provider: fix for target value duplication #2755

Merged

Conversation

skudriavtsev
Copy link
Contributor

Description

An extra target (with the same value) was added after retrieving actual state of A-records before sending updates to NIOS server, thus the next time a change necessity is detected, despite there was no real changes to endpoints.

Fixes #ISSUE

Checklist

  • Unit tests updated
  • End user documentation updated

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels May 12, 2022
@k8s-ci-robot k8s-ci-robot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label May 12, 2022
@k8s-ci-robot k8s-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels May 12, 2022
Copy link
Contributor

@stevehipwell stevehipwell left a comment

Choose a reason for hiding this comment

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

With the caveat that I'm not a "proper" maintainer here as my primary focus is the Helm chart, this PR looks good from a coding perspective and I could understand what the code was doing. I'm also not particularly familiar with Infoblox (worst reviewer ever) so I don't have much to add on the implementation other than my question about using an un-released version.

go.mod Outdated
@@ -27,7 +27,7 @@ require (
github.com/google/go-cmp v0.5.7
github.com/gophercloud/gophercloud v0.22.0
github.com/hooklift/gowsdl v0.5.0
github.com/infobloxopen/infoblox-go-client/v2 v2.1.1
github.com/infobloxopen/infoblox-go-client/v2 v2.1.2-0.20220401192150-b6079a2c974a
Copy link
Contributor

Choose a reason for hiding this comment

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

This doesn't look like an official release, is there some context behind this?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

There was no official release of go-client so far, after v2.1.1, thus I had to use this intermediate version, which includes the new feature which will be needed in the nearest future. Current full code is here: https://github.com/skudriavtsev/external-dns-1/commits/client-cert-auth This PR contains just a portion to fix particular issue.

Thanks for the comment. Anyway, the version v2.1.2-0.20220401192150-b6079a2c974a is not right, it contains a typo. I have bumped it up already.

@ranjishmp
Copy link

@seanmalloy cc @Raffo Can you please review this PR ?

@Raffo
Copy link
Contributor

Raffo commented May 25, 2022

/approve
/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label May 25, 2022
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Raffo, skudriavtsev

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 25, 2022
@k8s-ci-robot k8s-ci-robot merged commit f1e8ee3 into kubernetes-sigs:master May 25, 2022
@alebedev87 alebedev87 mentioned this pull request Jun 21, 2022
@nickperry
Copy link

The bug that this PR introduced was catastrophic. What changes to testing and review procedure could have caught it before it got merged?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants