Skip to content
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

Conversation

yaacov
Copy link
Member

@yaacov yaacov commented Aug 31, 2020

The correct list of supported models is: e1000e and virtio

Screenshots:
Before:
Peek 2020-08-31 14-26
After:
Peek 2020-08-31 14-29

@openshift-ci-robot openshift-ci-robot added bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. labels Aug 31, 2020
@openshift-ci-robot
Copy link
Contributor

@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
  • bug is open, matching expected state (open)
  • bug target release (4.6.0) matches configured target release for branch (4.6.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

In response to this:

Bug 1869620: kubevirt support only e1000e and virtio

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 openshift-ci-robot added the component/kubevirt Related to kubevirt-plugin label Aug 31, 2020
@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 31, 2020
@yaacov
Copy link
Member Author

yaacov commented Aug 31, 2020

@suomiy @pcbailey @irosenzw @glekner please review

@openshift-ci-robot
Copy link
Contributor

@yaacov: This pull request references Bugzilla bug 1869620, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.6.0) matches configured target release for branch (4.6.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

In response to this:

Bug 1869620: kubevirt support only e1000e and virtio

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');
Copy link
Member

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.

Copy link
Member Author

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(
Copy link
Member

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

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok

Copy link
Member Author

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',
Copy link
Member

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

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok

@yaacov yaacov force-pushed the kubevirt-support-only-e1000e-and-virtio branch from e57bb3a to a43cde8 Compare August 31, 2020 13:32
@openshift-ci-robot
Copy link
Contributor

@yaacov: This pull request references Bugzilla bug 1869620, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.6.0) matches configured target release for branch (4.6.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

In response to this:

Bug 1869620: kubevirt support only e1000e and virtio

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
Copy link
Member Author

yaacov commented Aug 31, 2020

/test e2e-gcp-console

@yaacov
Copy link
Member Author

yaacov commented Aug 31, 2020

/retest

@@ -27,10 +37,16 @@ export class NetworkInterfaceModel extends ObjectEnum<string> {
static fromString = (model: string): NetworkInterfaceModel =>
NetworkInterfaceModel.stringMapper[model];

isDeprecated = () => this.deprecated;
Copy link
Member

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.

Copy link
Member Author

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())
Copy link
Member

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

Copy link
Member Author

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(),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
ifaceModel.isSupported() || ifaceModel.toString() === model.toString(),
ifaceModel.isSupported() || ifaceModel === model,

you can just compare - plus no NPE will occur

@atiratree
Copy link
Member

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Sep 3, 2020
@openshift-ci-robot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

1 similar comment
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit 20c1c18 into openshift:master Sep 3, 2020
@openshift-ci-robot
Copy link
Contributor

@yaacov: All pull requests linked via external trackers have merged:

Bugzilla bug 1869620 has been moved to the MODIFIED state.

In response to this:

Bug 1869620: kubevirt support only e1000e and virtio

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 spadgett added this to the v4.6 milestone Sep 11, 2020
@yaacov
Copy link
Member Author

yaacov commented Sep 15, 2020

/cherrypick release-4.5

@openshift-cherrypick-robot

@yaacov: new pull request created: #6622

In response to this:

/cherrypick release-4.5

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. component/kubevirt Related to kubevirt-plugin lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants