Bug 826599
| Summary: | [RHEVM] [backend] [Required Networks] inappropriate error message when VM fails to start because of missing optional network | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Martin Pavlik <mpavlik> | ||||||
| Component: | ovirt-engine | Assignee: | lpeer <lpeer> | ||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Martin Pavlik <mpavlik> | ||||||
| Severity: | low | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 3.1.0 | CC: | dyasny, gklein, iheim, lpeer, ofrenkel, Rhev-m-bugs, yeylon, ykaul | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | network | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2012-08-19 12:22:53 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: | |||||||||
| Attachments: |
|
||||||||
Created attachment 587765 [details]
screenshot of error message
*** This bug has been marked as a duplicate of bug 841586 *** |
Created attachment 587764 [details] vdsm.log + engine.log Description of problem: when user tries to start VM on host which is missing optional network following error message appears: VM winXP is down. Exit message: Cannot get interface MTU on 'nonRequired': No such device. From this message it is not very cleat what is the real problem. That VM which is started has NIC/NICs attached to non-required network which is not attched to host. Version-Release number of selected component (if applicable): oVirt Enterprise Virtualization Engine Manager Version: 3.1.0_0001-11.el6ev How reproducible: 100% Steps to Reproduce: 1. Create logcial network and attach to cluster 2. configure new network as required=false 3. create VM, attach new network to VM, try to start VM Actual results: VM winXP is down. Exit message: Cannot get interface MTU on 'nonRequired': No such device. Expected results: Message which describes what the problem is more precisely, e.g. VM $VM is failed to start. VM $VM has attached network $network which is not attached to host $host. Additional info: error which is displayed in events comes from libvirt Thread-2418::ERROR::2012-05-30 13:53:24,290::vm::601::vm.Vm:_startUnderlyingVm) vmId=`e81eb68f-e3d6-471f-a003-c89118e97457`::The vm start process failed Traceback (most recent call last): File "/usr/share/vdsm/vm.py", line 567, in _startUnderlyingVm self._run() File "/usr/share/vdsm/libvirtvm.py", line 1365, in _run self._connection.createXML(domxml, flags), File "/usr/lib/python2.6/site-packages/vdsm/libvirtconnection.py", line 82, in wrapper ret = f(*args, **kwargs) File "/usr/lib64/python2.6/site-packages/libvirt.py", line 2486, in createXML if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=self) libvirtError: Cannot get interface MTU on 'nonRequired': No such device