Project

General

Profile

Actions

Bug #5132

closed

Unable to provision new ovirt compute resource system,

Added by Darrell Budic about 10 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Compute resources
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Using the 1.5 nightlies (fresh install, last tested 4/9/14) for the ovirt support, I'm unable to properly provision hosts. After creating the host in Foreman, once I hit Submit, it does the setup, and then hangs at the barber pole of "running - Power up". It creates the new VM on ovirt, but does NOT power it on:

create In Progress
completed - Set up compute instance znc.int
completed - Query instance details for znc.int
completed - Create DHCP Settings for znc.int
completed - TFTP Settings for znc.int
completed - Fetch TFTP boot files for znc.int
running - Power up compute instance znc.int
(======= 80% complete barber pole here )

Manually powering on the VM causes it to boot and begin a kickstart, but when it gets to the point where it tries to pull the kickstart file from foreman, it fails because foreman can't find the host by token, hostname, or ip address.

After the initial attempt times out, it fails the provisioning, and if you save it again, you get a host screen for a host still in build mode. It also deletes the VM. However, it can now produce the kickstart file by any method, and if you recreate the VM by hand (with same mac for dhcp of course), it will provision properly and become managed.

So problem 1: fails to start VM on ovirt computer resource. Problem 2, possibly related if it's not saving something until the power on completes, kickstart file not available until after initial provisioning fails.


Related issues 1 (0 open1 closed)

Related to Foreman - Refactor #5475: Revert #5132 oVirt volume fixResolvedActions
Actions

Also available in: Atom PDF