Bug 1301349 - [SR-IOV] - vdsm should persist and restore the number of enabled VFs on a PF during reboots
Summary: [SR-IOV] - vdsm should persist and restore the number of enabled VFs on a PF ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Network
Version: 3.6.2.5
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ovirt-3.6.3
: 3.6.3
Assignee: Dan Kenigsberg
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-24 12:14 UTC by Michael Burman
Modified: 2016-02-18 11:19 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-18 11:19:40 UTC
oVirt Team: Network
Embargoed:
rule-engine: ovirt-3.6.z+
rule-engine: exception+
ylavi: planning_ack+
danken: devel_ack+
rule-engine: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 52655 0 master MERGED restore-net: _get_persisted_numvfs 2016-01-24 16:02:45 UTC
oVirt gerrit 52665 0 ovirt-3.6 MERGED restore-net: _get_persisted_numvfs 2016-01-26 08:17:38 UTC

Description Michael Burman 2016-01-24 12:14:41 UTC 
Description of problem:
[SR-IOV] - vdsm should persist and restore the number of enabled VFs on a PF during reboots.

vdsm should take care for persisting and restoring enabled VFs on a PF during the HW reboots. 
Number of VFs should be persistent after reboots. 

from supervdsm.log -->
restore-net::ERROR::2015-11-11 15:07:09,986::vdsm-restore-net-config::68::root::(_get_persisted_numvfs)
Phisycal device in 0000:05:00.1 no longer exists. Skipping numvfs restoration.
restore-net::INFO::2015-11-11 15:07:09,986::vdsm-restore-net-config::86::root::(_restore_sriov_numvfs) SRIOV network device which is not persisted found at: 0000:05:00.1.

It used to work on previous 3.6 versions. 


Version-Release number of selected component (if applicable):
3.6.2.6-0.1.el6
vdsm-4.17.18-0.el7ev.noarch

How reproducible:
100

Steps to Reproduce:
1. Enable few VFs on a capable sr-iov server via setup networks dialog
2. Reboot the server

Actual results:
vdsm skipping numvfs restoration because the physical device no longer exists.

Expected results:
vdsm should restore and persist the numvfs during reboots.
Comment 1 Michael Burman 2016-01-31 10:22:59 UTC 
Verified on - 3.6.3-0.1.el6 and vdsm-4.17.19-0.el7ev.noarch
Note You need to log in before you can comment on or make changes to this bug.