-
Notifications
You must be signed in to change notification settings - Fork 462
Bug 1935539: vSphere: udp tnl workaround cannot use nmcli #2482
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 1935539: vSphere: udp tnl workaround cannot use nmcli #2482
Conversation
In testing this evening with openshift-sdn based install nmcli does not change the ethtool features until the interface has been restarted. Switching to using ethtool directly.
|
@jcpowermac: This pull request references Bugzilla bug 1935539, which is invalid:
Comment DetailsIn 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. |
|
fyi: @wking |
|
/cherry-pick release-4.7 |
|
@jcpowermac: once the present PR merges, I will cherry-pick it on top of release-4.7 in a new PR and assign it to you. DetailsIn 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 |
I tested a clean install which incorporated this PR and confirmed that |
|
/bugzilla refresh |
|
@wking: This pull request references Bugzilla bug 1935539, which is valid. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Bugzilla (huirwang@redhat.com), skipping review request. DetailsIn 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 |
|
/hold |
|
Yes, of course when you just change the properties NM doesn't live-mirror those changes. You need to intentionally tell NM to do that, because you (as the person changing the config) know better than NM when those changes should be applied. Have you tried |
|
Lastly, this shouldn't be a dispatcher script. It should be an MCO systemd unit (like ovs-configuration.sh) that targets only vmxnet3 devices, and runs on system startup (or even better, before reboot!) once to disable offload property and then reapply the connection. Changes made with nmcli should be persistent. |
|
To target vmxnet3 sh-4.4# nmcli -f general.driver dev show ens192
GENERAL.DRIVER: vmxnet3 |
|
Something like: |
|
|
might be easier to add the ethtool to |
|
/retest |
Maybe we can ignore this error. If we run this once on boot via systemd, then it shouldn't re-run, maybe. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
last update job only failed |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
Letting this last run retry, will check in after. |
|
running out of leases again for GCP for the agnostic-upgrade job: 2021/03/25 17:02:23 error: Failed to acquire resource, current capacity: 0 free, 70 leased |
|
/retest |
|
@kikisdeliveryservice would you be ok with overriding now? |
|
Given the severity of the bug, the fact that this PR changes aren't implicated in the job failure, and the red-ness of the job. We can make a one time exception and override. 😄 /override ci/prow/e2e-agnostic-upgrade |
|
@kikisdeliveryservice: Overrode contexts on behalf of kikisdeliveryservice: ci/prow/e2e-agnostic-upgrade DetailsIn 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 Please review the full test history for this PR and help us cut down flakes. |
6 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. |
|
/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. |
|
/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. |
|
lol, this must be the most built 5 lines of codes in history :-) |
|
/skip |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@jcpowermac: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@jcpowermac: All pull requests linked via external trackers have merged: Bugzilla bug 1935539 has been moved to the MODIFIED state. DetailsIn 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. |
|
@jcpowermac: #2482 failed to apply on top of branch "release-4.7": DetailsIn 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. |
backport PR: openshift#2482 There is an issue (tbd) with the VMXNET3 v4 driver causing network traffic between various openshift services to be dropped. With the addition of VMXNET3 v4 in RHCOS 4.7 (RHEL 8.3 kernel) this workaround needs to be in place for customers running on vSphere 6.7, OpenShift 4.7 and virtual hardware version 14 or higher.
In testing this evening with openshift-sdn based install
nmcli does not change the ethtool features until the
interface has been restarted.
Switching to using ethtool directly.