-
Notifications
You must be signed in to change notification settings - Fork 462
Bug 1952358: vsphere: platform none, vmxnet3v4 fix move to base #2559
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 1952358: vsphere: platform none, vmxnet3v4 fix move to base #2559
Conversation
|
@jcpowermac: This pull request references Bugzilla bug 1952358, 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
Requesting review from QA contact: 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. |
|
It'd be also good if we can at least manually verify this for |
Sounds like a good idea, let me do that. |
|
/test e2e-vsphere |
|
As requested tested a
Disabled udp offload as expected Dispatch file, as expected No cloud-config, as expected |
|
vSphere job failure caused by single tests, I would think unrelated to this change. |
|
Find this implementation better than #2558 . Can we also add description in commit message to include reasoning of this template move? |
|
/retest |
The template is being moved from `templates/common/vsphere` which is only applied when `platform: vsphere` is set. There are customers running `platform: none` on vSphere or ESXi directly that can be effected by the vmxnet3v4 issue.
bf130b1 to
0daceef
Compare
@sinnykumari updated. |
Failure could be infra issue. |
|
vsphere test failures look unrelated. |
|
/retest |
|
@jcpowermac: The following tests 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. |
|
Are we waiting for those last jobs to pass? From dealing with other PRs in MCO those rarely are green. Still going to take quite a bit of time for this to merge and then backported to 4.8 and 4.7. |
|
My $0.02: If we can explain why these are failing and have confidence this works then I don't believe we need to wait. |
yuqi-zhang
left a comment
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.
I think the failing CI are unrelated and not required, so let's go ahead and move forwards with this given
- Joseph was able to confirm this works on
none - This does not seem to affect any other platform
- We will be looking to revert this as soon as the underlying issues are resolved
/lgtm
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jcpowermac, yuqi-zhang The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@jcpowermac: All pull requests linked via external trackers have merged: Bugzilla bug 1952358 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. |
|
@cuppett: new pull request created: #2564 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. |
|
@cuppett: new pull request could not be created: failed to create pull request against openshift/machine-config-operator#release-4.7 from head openshift-cherrypick-robot:cherry-pick-2559-to-release-4.7: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for openshift-cherrypick-robot:cherry-pick-2559-to-release-4.7."}],"documentation_url":"https://docs.github.com/rest/reference/pulls#create-a-pull-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. |
Alternative to #2558