Bug 1310410 - Functional test failures with persistence set to ifcfg
Summary: Functional test failures with persistence set to ifcfg
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: vdsm
Classification: oVirt
Component: Core
Version: 4.18.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ovirt-3.6.5
: 4.17.26
Assignee: Edward Haas
QA Contact: Meni Yakove
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-21 12:15 UTC by Edward Haas
Modified: 2016-04-21 14:38 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-21 14:38:28 UTC
oVirt Team: Network
Embargoed:
danken: ovirt-3.6.z?
rule-engine: planning_ack?
danken: devel_ack+
rule-engine: testing_ack+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 53763 0 ovirt-3.6 MERGED net: api: use running config only with unified persistence 2016-02-23 11:51:57 UTC
oVirt gerrit 53770 0 ovirt-3.6 MERGED net tests: Clean net & bond after functional test. 2016-02-23 08:47:10 UTC
oVirt gerrit 53775 0 ovirt-3.6 MERGED net tests: make functional tests run again with persistence=ifcfg 2016-02-23 11:51:33 UTC
oVirt gerrit 53818 0 ovirt-3.6 MERGED netinfo: do not mistake a veth device for a VLAN in ifaceUsed 2016-02-25 11:34:05 UTC
oVirt gerrit 53827 0 ovirt-3.6 MERGED net: Fix dhcp reporting 2016-02-25 11:34:42 UTC

Description Edward Haas 2016-02-21 12:15:28 UTC
Description of problem:
When setting 'net_configurator = ifcfg' in vdsm.conf, functional tests are failing.

How reproducible:
Run functional tests with 'net_configurator = ifcfg'.

Actual results:
Tests fail

Expected results:
Tests pass

Comment 1 Red Hat Bugzilla Rules Engine 2016-02-21 12:15:34 UTC
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.

Comment 2 Eyal Edri 2016-03-31 08:35:54 UTC
Bugs moved pre-mature to ON_QA since they didn't have target release.
Notice that only bugs with a set target release will move to ON_QA.


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