Bug 1308839
| Summary: | [vmfex-hook] - Failed to run VM with vdsm-hook-vmfex-dev-4.17.20 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] vdsm | Reporter: | Michael Burman <mburman> | ||||
| Component: | Core | Assignee: | Dan Kenigsberg <danken> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Michael Burman <mburman> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 4.17.20 | CC: | bugs, gklein, ylavi | ||||
| Target Milestone: | ovirt-3.6.4 | Keywords: | Regression | ||||
| Target Release: | 4.17.23 | Flags: | rule-engine:
ovirt-3.6.z+
rule-engine: blocker+ ylavi: planning_ack+ danken: devel_ack+ rule-engine: testing_ack+ |
||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | v4.17.23.1 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-04-05 13:53:27 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Network | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1305338 | ||||||
| Attachments: |
|
||||||
libvirt-1.2.17-13.el7_2.3.x86_64 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. This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP. This patch has actually made it into vdsm-4.17.23.1, which is testable now. Verified on - 3.6.4-0.1.el6 and vdsm-4.17.23.1-0.el7ev.noarch |
Created attachment 1127543 [details] vdsm log Description of problem: [vmfex-hook] - Failed to run VM with vdsm-hook-vmfex-dev-4.17.20 Thread-115::ERROR::2016-02-16 10:40:20,087::vm::759::virt.vm::(_startUnderlyingVm) vmId=`404f96db-b224-4163-a21e-eeb8eb084d7b`::The vm start process failed Traceback (most recent call last): File "/usr/share/vdsm/virt/vm.py", line 703, in _startUnderlyingVm self._run() File "/usr/share/vdsm/virt/vm.py", line 1941, in _run self._connection.createXML(domxml, flags), File "/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py", line 124, in wrapper ret = f(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 1313, in wrapper return func(inst, *args, **kwargs) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3611, in createXML if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=self) libvirtError: unsupported configuration: filterref is not supported for network interfaces of type direct Thread-115::INFO::2016-02-16 10:40:20,088::vm::1330::virt.vm::(setDownStatus) vmId=`404f96db-b224-4163-a21e-eeb8eb084d7b`::Changed state to Down: unsupported configuration: filterref is not supported for network interfaces of type direct (code=1) Version-Release number of selected component (if applicable): vdsm-hook-vmfex-dev-4.17.20-0.el7ev.noarch vdsm-4.17.20-0.el7ev.noarch How reproducible: 100 Steps to Reproduce: 1. Try to run VM using vmfex vNIC profile on a UCS server Actual results: Failed to run VM with error: "VM v4 is down with error. Exit message: unsupported configuration: filterref is not supported for network interfaces of type direct." Expected results: Should work and run as expected(as working on 3.5.8)