Project

General

Profile

Actions

Bug #1900

closed

foreman should honor ovirt template boot sequence

Added by viet nguyen over 11 years ago. Updated almost 11 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Host creation
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

I just want to create a host from pre-configured ovirt template with bootable disk. Foreman changes boot sequence to pxe which prevents the host from starting up. Can we make foreman just "work" out of the box for a simple use case?

Related to bug 1630


Files

foreman-new-host.png View foreman-new-host.png 45.4 KB viet nguyen, 11/08/2012 02:37 PM
Actions #1

Updated by Ohad Levy over 11 years ago

  • Status changed from New to Feedback

I'm not sure that makes any sense, if foreman is provisioning via PXE then it should not be the case, and if foreman is using an oVirt template, then it should configure it to boot from disk (however templates boot is not supported at the moment).

Actions #2

Updated by viet nguyen over 11 years ago

In our setup we don't have foreman control DHCP and PXE. I just want to go to foreman UI and create oVirt VMs. Unless I'm missing something obvious Foreman does not let me create oVirt VM from template. I'm not sure how you can create template-less (or from 'blank') VM in Foreman since the template field is always populated with ovirt templates.

Actions #3

Updated by viet nguyen over 11 years ago

It's working for me now. New Host -> Virtual Machine tab:
1. Add a network interface
2. Do not add new volume since oVirt template already has a bootable disk

Actions #4

Updated by Benjamin Papillon almost 11 years ago

  • Status changed from Feedback to Resolved

Hello,

Since It is working for you now, I'm closing this ticket. If you feel it is an error, please reopen it.

Regards,

Actions

Also available in: Atom PDF