Bug 907155
| Summary: | [engine][plugNic] Devices boot order not saved in the DB upon plug/unplug of a virtual NIC | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Mike Kolesnik <mkolesni> | ||||
| Component: | ovirt-engine | Assignee: | Mike Kolesnik <mkolesni> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Meni Yakove <myakove> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 3.2.0 | CC: | acathrow, dyasny, iheim, lpeer, masayag, Rhev-m-bugs, yeylon, ykaul | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 3.2.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | network | ||||||
| Fixed In Version: | SF7 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 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: |
|
||||||
Verified on rhevm-3.2.0-8.el6ev.noarch 3.2 has been released 3.2 has been released 3.2 has been released 3.2 has been released 3.2 has been released |
Created attachment 692310 [details] screenshot Description of problem: When plugging/unplugging a VM's NIC the devices boot order isn't updated in the DB. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Create a VM with an active NIC as first boot device 2. Unplug the NIC 3. Try to run the VM Actual results: The NIC will still be specified as 1st boot device in the libvirt XML but not appear since it's not plugged. You will get a nice error in the audit log: VM vm_on_fake3_2 is down. Exit message: internal error boot orders have to be contiguous and starting from 1. Expected results: VM should be able to run Additional info: This only happens on clusters where unplugging of devices is supported.