Project

General

Profile

Actions

Bug #5132

closed

Unable to provision new ovirt compute resource system,

Added by Darrell Budic almost 10 years ago. Updated over 5 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 #1

Updated by Yama Kasi almost 10 years ago

Hi,

I have seen the same issue on 1.5 RC1, have you been able to solve this ?

Actions #2

Updated by Ohad Levy almost 10 years ago

which version of ovirt are you using?

Actions #3

Updated by Yama Kasi almost 10 years ago

I'm on oVirt 3.4.

Actions #4

Updated by Yama Kasi almost 10 years ago

Hi Guys.

This just seems to "work" again as it did before on this same install.

I didn't change a thing here.... so I will report when it's happening again...

No clue yet!

Actions #5

Updated by Ohad Levy almost 10 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Amos Benari
  • Priority changed from High to Normal
  • Target version set to 1.8.3
Actions #6

Updated by Dominic Cleal almost 10 years ago

  • translation missing: en.field_release set to 4
Actions #7

Updated by Dominic Cleal almost 10 years ago

Actions #8

Updated by Amos Benari almost 10 years ago

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

Updated by Dominic Cleal almost 10 years ago

For reference, 5f58478b95ffd51eb41f53718e09c03a3613c827 was also linked to this issue but should have been #5389.

Actions #10

Updated by Darrell Budic almost 10 years ago

Finally got a chance to test and can confirm that this has been fixed for me in nightlies. Thanks!

Actions #11

Updated by Dominic Cleal almost 10 years ago

  • translation missing: en.field_release changed from 4 to 17
Actions

Also available in: Atom PDF