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

Improve IPv6 testing and minor fixes #660

Merged
merged 4 commits into from Jun 5, 2020

Conversation

aojea
Copy link
Contributor

@aojea aojea commented Jun 4, 2020

Aggregated several commits in the PR because I was finding several issues.

It was reported that the cluster-network-operator wasn't configuring correctly kube-proxy bind-address if it was "::", so I added some unit tests to check that it works correctly.

The other fixes are explained in the commit messages.

aojea and others added 3 commits June 4, 2020 20:16
the function checks if the IP is invalid, but instead of returning
and empty value, it logs the error and returns the invalid value

Signed-off-by: Antonio Ojea <aojea@redhat.com>
the getAddressAndPort method was using a signed integer with 16
bits to convert the port string to a number, thus only
-32,768 to 32,767 were allowed.

Using an unsigned integer with 16 bits solves the problem

Signed-off-by: Antonio Ojea <aojea@redhat.com>
IPv6 addresses must be enclosed in square brackets when used in
address:port format.

Signed-off-by: Antonio Ojea <aojea@redhat.com>
@aojea
Copy link
Contributor Author

aojea commented Jun 4, 2020

/assign @dcbw @danwinship

@rcarrillocruz
Copy link
Contributor

you may want to rebase to single commit

@aojea
Copy link
Contributor Author

aojea commented Jun 4, 2020

you may want to rebase to single commit

I prefer not to, since every commit is totally independent and, in case of an error, it will be easier to revert just the offending one.

pkg/network/kube_proxy_test.go Show resolved Hide resolved
pkg/network/kube_proxy_test.go Outdated Show resolved Hide resolved
@danwinship
Copy link
Contributor

you may want to rebase to single commit

I prefer not to, since every commit is totally independent and, in case of an error, it will be easier to revert just the offending one.

yeah. We don't want PRs with one real commit and a bunch of fixes to it, but if the commit is logically made up of multiple pieces, go with multiple commits

Signed-off-by: Antonio Ojea <aojea@redhat.com>
@aojea
Copy link
Contributor Author

aojea commented Jun 5, 2020

/retest

@danwinship
Copy link
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jun 5, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aojea, danwinship

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

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 5, 2020
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

6 similar comments
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jun 5, 2020

@aojea: The following test failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/e2e-vsphere 5216117 link /test e2e-vsphere

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit 15d9c13 into openshift:master Jun 5, 2020
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. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants