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 1869620: kubevirt support only e1000e and virtio #6479
Bug 1869620: kubevirt support only e1000e and virtio #6479
Conversation
@yaacov: This pull request references Bugzilla bug 1869620, 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. |
@yaacov: This pull request references Bugzilla bug 1869620, which is valid. 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. |
@@ -4,11 +4,7 @@ import { READABLE_VIRTIO } from '../constants'; | |||
|
|||
export class NetworkInterfaceModel extends ObjectEnum<string> { | |||
static readonly VIRTIO = new NetworkInterfaceModel('virtio'); | |||
static readonly E1000 = new NetworkInterfaceModel('e1000'); |
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.
they are still valid values (you can still have a VM with these models). Can you please just mark them as not supported? Similar to what we do in DiskType enum? And filter them in places where we use them.
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.
using the deprecation logic like in disks :-)
@@ -3,18 +3,15 @@ import { ObjectEnum } from '../../object-enum'; | |||
import { NetworkInterfaceModel } from '../../vm/network'; | |||
|
|||
export class OvirtNetworkInterfaceModel extends ObjectEnum<string> { | |||
static readonly E1000 = new OvirtNetworkInterfaceModel('e1000', NetworkInterfaceModel.E1000); | |||
static readonly E1000 = new OvirtNetworkInterfaceModel('e1000', NetworkInterfaceModel.E1000E); | |||
static readonly PCI_PASSTHROUGH = new OvirtNetworkInterfaceModel( |
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.
let's wait first until discussion in https://bugzilla.redhat.com/show_bug.cgi?id=1869208 is resolved
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.
ok
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.
https://bugzilla.redhat.com/show_bug.cgi?id=1869208 is resolved as wont fix.
a. the API will continue to accept the unsupported cards,
b. Once Import operator will merge (or not) a fix that will map unsupported network cards, we will could fix our mapping accordingly.
@@ -50,11 +50,7 @@ export enum VM_STATUS { | |||
// Network | |||
export enum NIC_MODEL { | |||
VirtIO = 'VirtIO', | |||
e1000 = 'e1000', |
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 suppose we don't need it for testing, but it doesn't hurt to have it here
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.
ok
e57bb3a
to
a43cde8
Compare
@yaacov: This pull request references Bugzilla bug 1869620, which is valid. 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. |
/test e2e-gcp-console |
/retest |
@@ -27,10 +37,16 @@ export class NetworkInterfaceModel extends ObjectEnum<string> { | |||
static fromString = (model: string): NetworkInterfaceModel => | |||
NetworkInterfaceModel.stringMapper[model]; | |||
|
|||
isDeprecated = () => this.deprecated; |
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 rather call it isSupported
since the value still can be used (but shouldn't in the UI)? This is a probably different semantic than floppy.
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.
ok :-)
); | ||
})} | ||
{NetworkInterfaceModel.getAll() | ||
.filter((ifaceModel) => ifaceModel.isSupported()) |
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 show the unsupported one if it is already selected in the beginning
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.
added a filter exception 👍
{NetworkInterfaceModel.getAll() | ||
.filter( | ||
(ifaceModel) => | ||
ifaceModel.isSupported() || ifaceModel.toString() === model.toString(), |
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.
ifaceModel.isSupported() || ifaceModel.toString() === model.toString(), | |
ifaceModel.isSupported() || ifaceModel === model, |
you can just compare - plus no NPE will occur
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: suomiy, yaacov 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 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. |
@yaacov: All pull requests linked via external trackers have merged: Bugzilla bug 1869620 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. |
/cherrypick release-4.5 |
@yaacov: new pull request created: #6622 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. |
The correct list of supported models is: e1000e and virtio
Screenshots:
Before:
After: