Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1142871 - foreman host provisioning never finishes [NEEDINFO]
Summary: foreman host provisioning never finishes
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: 3.5
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: 3.5.1
Assignee: Yaniv Bronhaim
QA Contact: Pavel Stehlik
URL:
Whiteboard: infra
Depends On:
Blocks: 1083998
TreeView+ depends on / blocked
 
Reported: 2014-09-17 14:31 UTC by Netbulae
Modified: 2016-02-10 19:34 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-10-23 12:22:15 UTC
oVirt Team: Infra
ybronhei: needinfo? (info)


Attachments (Terms of Use)
logfiles (deleted)
2014-09-22 12:43 UTC, Netbulae
no flags Details

Description Netbulae 2014-09-17 14:31:12 UTC
Description of problem:
Provisioning a new host using the foreman discovered host process never finishes and the status remains on  "Installing OS"

When I remove the host from ovirt and add it again, the host is enabled and changes to UP state.

Version-Release number of selected component (if applicable):
3.5rc2

Comment 1 Oved Ourfali 2014-09-20 05:36:29 UTC
Can you provide the ovirt and Foreman logs?

Comment 2 Yaniv Bronhaim 2014-09-20 07:23:20 UTC
It means that the ovirt_provision_plugin didn't run. first check in your foreman's about page, under plugins if you installed properly the ovirt_provision_plugin 

If yes, please attach the production.log file from your foreman setup and the engine.log and we'll check if the automatic call ran after the host was provisioned.

thanks

Comment 3 Netbulae 2014-09-22 12:36:00 UTC
I cannot find anything in the engine.log or production.log, but you can check for yourself.

How do I identify this automatic call?

Comment 4 Netbulae 2014-09-22 12:43:00 UTC
Created attachment 939986 [details]
logfiles

Comment 5 Netbulae 2014-09-22 14:02:07 UTC
Is this the correct version?

ovirt_provision_plugin 		Yaniv Bronhaim 	0.0.1

Comment 6 Yaniv Bronhaim 2014-09-28 13:07:46 UTC
yes this is fine. and you have some failures in the production log

can you try turning on debug log and try that again?

http://projects.theforeman.org/projects/foreman/wiki/Troubleshooting#How-do-I-enable-debugging

except that, you also need to add the puppet class for the engine's authentication key. did you do that?

Comment 7 Oved Ourfali 2014-10-23 12:22:15 UTC
Reducing priority. This isn't urgent, and we haven't heard on another use-case in which it happened.

We waited a while for additional info.
Closing for now.
If relevant, please reopen.

Comment 8 Netbulae 2014-10-23 12:39:23 UTC
Yes, not urgent as I still have to find time to reproduce....

Probably early next week


Note You need to log in before you can comment on or make changes to this bug.