Bug 1007811 - ovirt-node install process hang on progress_page
Summary: ovirt-node install process hang on progress_page
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-node
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Fabian Deutsch
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: ovirt-node-3.1
TreeView+ depends on / blocked
 
Reported: 2013-09-13 11:17 UTC by haiyang,dong
Modified: 2013-11-28 11:55 UTC (History)
14 users (show)

Fixed In Version: ovirt-node-3.0.3
Clone Of:
Environment:
Last Closed: 2013-11-28 11:55:03 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)
attached Screenshot (7.50 KB, image/png)
2013-09-13 11:17 UTC, haiyang,dong
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 19320 0 None None None Never

Description haiyang,dong 2013-09-13 11:17:04 UTC
Created attachment 797287 [details]
attached Screenshot

Description of problem:
ovirt-node install process hang on progress_page(Seen progress_page.png)


Version-Release number of selected component (if applicable):
ovirt-node-iso-3.1.0-0.999.999.20130913101853git56550df.585.fc18.iso

How reproducible:
100% 
 
Steps to Reproduce:

Actual result:


Expect result:


Additional info:

--

Comment 1 Mike Burns 2013-09-13 12:01:09 UTC
I hesitant to really spend a lot of time on this since we're planning on re-writing most of the installation process in 3.1.  We'll also be dropping F18 images in 3.1.  

Joey, can you take a quick look?  If there isn't anything obvious, let's see hold off until we get f19/f20 images and get the installer re-written.

Comment 2 Fabian Deutsch 2013-09-17 09:34:50 UTC
(In reply to Mike Burns from comment #1)
> I hesitant to really spend a lot of time on this since we're planning on
> re-writing most of the installation process in 3.1.  We'll also be dropping
> F18 images in 3.1.  

This is a regression from 3.0. It also affects our F19 builds and will be a problem in node-3.1 release.

Good thing is that we discovered it early in the 3.1 cycle ;)

Comment 3 Fabian Deutsch 2013-09-17 10:32:01 UTC
The problem was three fold:
1. Difficult debugging due to insufficient debugging informations from the installer thread (fixed in http://gerrit.ovirt.org/19317
2. An copy and paste error (fixed in http://gerrit.ovirt.org/19319)
3. The password page didn't remeber the password which was entered (fix in http://gerrit.ovirt.org/19320)

Comment 4 Fabian Deutsch 2013-09-17 10:33:00 UTC
Also merged this patches to unblock upstream testing.


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