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
Bug 1794546: Console-1933: IPv6 support (simpler alternative) #375
Bug 1794546: Console-1933: IPv6 support (simpler alternative) #375
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# IPv6 should handle IPv4 passively so long as it is not bound to a | ||
# specific address or set to IPv6_ONLY | ||
# https://stackoverflow.com/questions/25817848/python-3-does-http-server-support-ipv6 | ||
addr = ('::', 8080) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should confirm that ::
doesn't break ipv4. It's not clear to me from the stack overflow thread
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if it breaks ipv4 will it not fail our CI jobs?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup, we have e2e tests for this so it would fail CI if this is a problem.
I ran it in my cluster, was able to verify downloads still download via the UI. pod is running, etc. I think we are good.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we configure nodes with the ipv6.disable=1
kernel command line and see what happens if we blacklist the ipv6 kernel module (via an MC?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, this will most likely fail if ipv6_disable
. Go-based code doesn't have to worry about that because go has code to deal with that and fall back to 0.0.0.0
if you try to bind to ::
but IPv6 is unavailable.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So do we need to hold on this, or make a bug for follow?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can resolve this by going back to dynamically changing the downloader based on whether the cluster was configured for IPv6 or not.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, this inline python script is not great for any kind of additional complexity. Sounds like an overhaul of the downloads bit.
@benjaminapetersen Do we have any CLI download test coverage in CI? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/retest |
@spadgett yes, we have: We could potentially add one in console to also verify the downloads links do respond with files:
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: benjaminapetersen, spadgett 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 |
/retest
|
/cherry-pick release-4.3 This should backport cleanly. Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1794548 |
@benjaminapetersen: once the present PR merges, I will cherry-pick it on top of release-4.3 in a new PR and assign it to you. In response to this:
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. |
@benjaminapetersen: This pull request references Bugzilla bug 1794546, which is invalid:
Comment In response to this:
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. |
/bugzilla refresh |
@benjaminapetersen: This pull request references Bugzilla bug 1794546, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. In response to this:
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. |
/retest
|
/retest unexpected flake:
will keep an eye on that. |
/retest
|
/hold cancel |
/retest Please review the full test history for this PR and help us cut down flakes. |
2 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
@benjaminapetersen: All pull requests linked via external trackers have merged. Bugzilla bug 1794546 has been moved to the MODIFIED state. In response to this:
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. |
@benjaminapetersen: #375 failed to apply on top of branch "release-4.3":
In response to this:
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. |
Have you filed a bug somewhere to follow-up on the issue raised by @eparis, where this would break on a host with IPv6 disabled? |
Created this bug: I am presently uncertain about the severity & will be fishing around for further details. |
Simpler/preferred change over #374
RE doc changes needed
/assign @russellb
/cc @spadgett @jhadvig
bindNetwork: "tcp"
network.config.openshift.io