Bug 1907707 - SR-IOV: secondary interface comes and goes in vmi status
Summary: SR-IOV: secondary interface comes and goes in vmi status
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Networking
Version: 2.6.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.8.0
Assignee: Petr Horáček
QA Contact: Ofir Nash
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-12-15 02:46 UTC by yzaindbe
Modified: 2021-07-27 14:24 UTC (History)
3 users (show)

Fixed In Version: virt-launcher-container-v4.8.0-57
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-07-27 14:22:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
config yamls (2.22 KB, text/plain)
2020-12-15 02:46 UTC, yzaindbe
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2021:2920 0 None None None 2021-07-27 14:24:23 UTC

Description yzaindbe 2020-12-15 02:46:15 UTC
Created attachment 1739214 [details]
config yamls

Description of problem:
creating a vm with sriov secondary interface, the interface is sometimes shown
for a few minutes and then gone for a few minutes.

Version-Release number of selected component (if applicable):
OCP 4.6.1
CNV 2.6.0

How reproducible:
Always

Steps to Reproduce:
1. install sriov operator

2. label sriov capable worker nodes with 'feature.node.kubernetes.io/network-sriov.capable: "true"'
(you can find them by using 'oc get sriovnetworknodestate'

3.apply attached configurations (name of pfNames in the policy needs to fit the suitable sriov nics on the nodes)

Actual results:
sometimes you see and sometimes you dont see the secondary interface in the vmi yaml

Expected results:
always see all interfaces

Additional info:

Comment 3 oshoval 2021-05-18 07:15:25 UTC
PR that should fix it https://github.com/kubevirt/kubevirt/pull/5560

Comment 4 Petr Horáček 2021-05-18 07:20:23 UTC
Moving back to POST, MODIFIED means that the code got merged on the relevant release (4.8).

Comment 5 Ofir Nash 2021-05-27 16:17:18 UTC
Verified. Scenario checked:

1. Labeled sriov worker nodes:
[cnv-qe-jenkins@cnvqe-08 ofir]$ oc get sriovnetworknodestate -A
NAMESPACE                          NAME                               AGE
openshift-sriov-network-operator   cnvqe-10.lab.eng.tlv2.redhat.com   72d
openshift-sriov-network-operator   cnvqe-11.lab.eng.tlv2.redhat.com   72d

oc label node cnvqe-10/11.lab.eng.tlv2.redhat.com feature.node.kubernetes.io/network-sriov.capable=true


2. Applied the three configuration that were attached: SriovNetworkNodePolicy, SriovNetwork and VirtualMachineInstance
(In the last configuration (VirtualMachineInstance), need to add namespace attribute as it is missing: "namespace: openshift-sriov-network-operator").
oc apply -f <ConfigurationsNames.yaml>

3. Verified secondary interface shows up in the vmi yaml created:
oc get vmi -n openshift-sriov-network-operator vmi-sriov -o yaml

interfaces:
  - interfaceName: eth0
    ipAddress: 10.128.2.139
    ipAddresses:
    - 10.128.2.139
    mac: 52:54:00:33:15:bd
    name: default
  - interfaceName: eth1
    ipAddress: 10.200.3.1
    ipAddresses:
    - 10.200.3.1
    - 2620:52:0:2e29:1:ff:fe00:0
    - fe80::1:ff:fe00:0
    mac: "02:01:00:00:00:00"
    name: example-sriovnetwork

Comment 8 errata-xmlrpc 2021-07-27 14:22:32 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Virtualization 4.8.0 Images), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:2920


Note You need to log in before you can comment on or make changes to this bug.