Bug 1209038

Summary:	RunOnce boot sequence is persisted after removing & adding network
Product:	[oVirt] ovirt-engine	Reporter:	Shmuel Melamud <smelamud>
Component:	General	Assignee:	Shmuel Melamud <smelamud>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jiri Belka <jbelka>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	---	CC:	bugs, ecohen, gklein, jas, jbelka, lsurette, michal.skrivanek, rbalakri, s.kieske, yeylon
Target Milestone:	ovirt-3.6.0-rc	Flags:	rule-engine: ovirt-3.6.0+ ylavi: planning_ack+ rule-engine: devel_ack+ pnovotny: testing_ack+
Target Release:	3.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	virt
Fixed In Version:	ovirt-3.6.0-alpha1.2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-11-04 11:35:55 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Shmuel Melamud 2015-04-05 14:10:52 UTC

Steps to Reproduce:

1. Create a VM.
2. Set boot sequence for the VM as follows:
  First Device: Hard Disk
  Second Device: [None]
3. Add network to the VM.
4. Run Once the VM. In the Run Once dialog select the following boot sequence:
  First Device: Network (PXE)
  Second Device: Hard Disk
5. The VM is booting from the network.
6. Shutdown the VM.
7. Remove the network from the VM and add it again.
8. Verify that VM boot sequence is still as described in step 2.
9. Run the VM.

Actual results:

The VM is booting from the network.

Expected results:

The VM is booting from the hard disk.

Comment 1 Shmuel Melamud 2015-04-05 14:28:35 UTC

The problem is in VmDeviceCommonUtils.updateVmDevicesBootOrder() method that is called indirectly by AddVmInterfaceCommand.addInterfaceToDb(). The VmDeviceCommonUtils.updateVmDevicesBootOrder() uses RunOnce boot sequence if vm.isRunOnce() is true.

Comment 2 Jiri Belka 2015-10-26 15:50:00 UTC

ok, rhevm-webadmin-portal-3.6.0.2-0.1.el6.noarch

boot ok as described in #0

Comment 3 Sandro Bonazzola 2015-11-04 11:35:55 UTC

oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue.
If problems still persist, please open a new BZ and reference this one.