Bug 1846922: "downloads" pod does not work on the node which is disabled IPv6 #438
Conversation
openshift-ci-robot
added
the
bugzilla/severity-medium
|
@bysnupy: This pull request references Bugzilla bug 1846922, 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. |
openshift-ci-robot
added
the
bugzilla/invalid-bug
|
/bugzilla refresh |
openshift-ci-robot
added
the
bugzilla/valid-bug
|
@spadgett: This pull request references Bugzilla bug 1846922, 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. 3 validation(s) were run on this bug
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. |
openshift-ci-robot
removed
the
bugzilla/invalid-bug
|
/lgtm Not sure if we have CI coverage or not... |
When IPv6 is disabled, the socket binding will be failed, so we catch the exception and then IPv4 would use at that time. Reference: https://bugzilla.redhat.com/show_bug.cgi?id=1846922
|
@wking Could you label LGTM again ? the label has been removed due to late detection of the ci-bot for the changes. |
We do have some test coverage: https://github.com/openshift/console-operator/blob/master/test/e2e/downloads_test.go |
|
/cherry-pick release-4.5 |
|
@spadgett: once the present PR merges, I will cherry-pick it on top of release-4.5 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. |
|
/cherry-pick release-4.4 |
|
@spadgett: once the present PR merges, I will cherry-pick it on top of release-4.4 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. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bysnupy, jhadvig, wking 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 |
openshift-ci-robot
added
the
approved
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@bysnupy: All pull requests linked via external trackers have merged: openshift/console-operator#438. Bugzilla bug 1846922 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. |
|
@spadgett: new pull request created: #441 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. |
|
@spadgett: new pull request created: #442 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. |
When IPv6 is disabled, the socket binding will be failed, so we catch the exception and then IPv4 would use at that time.