Project

General

Profile

Bug #2610

Boot order is set incorrectly on oVirt/RHEV VM's when created with 1.2-RC1

Added by Jason Montleon about 6 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Dmitri Dolguikh
Category:
-
Target version:
1.2.0
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

When I create VM's in Foreman 1.2-RC1 the boot order is being set to first Hard Disk then Network (PXE).

This has the effect that when setting a host back to build to rebuild it, it just boots back to the OS rather than PXE booting.

Associated revisions

Revision e34f7136 (diff)
Added by Dmitri Dolguikh about 6 years ago

fixes #2610 - fixed the boot device order for oVirt VMs created in Foreman

Revision 0cb9ed6f (diff)
Added by Dmitri Dolguikh about 6 years ago

fixes #2610 - fixed the boot device order for oVirt VMs created in Foreman
(cherry picked from commit e34f713634a44986695f266ba442f2e07bfaea63)

History

#1 Updated by Dmitri Dolguikh about 6 years ago

  • Status changed from New to Assigned
  • Assignee set to Dmitri Dolguikh

#2 Updated by Dmitri Dolguikh about 6 years ago

  • Status changed from Assigned to Ready For Testing

#3 Updated by Dmitri Dolguikh about 6 years ago

We should probably have network, hd boot order in all VMs?

#4 Updated by Anonymous about 6 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#5 Updated by Jason Montleon about 6 years ago

Looks like this does fix the issue. Thanks!

Also available in: Atom PDF