Bug 1557780 - hosted-engine wizard is stuck on 'Loading wizard...'
Summary: hosted-engine wizard is stuck on 'Loading wizard...'
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: cockpit-ovirt
Classification: oVirt
Component: Hosted Engine
Version: 0.11.17
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ovirt-4.2.2
: ---
Assignee: Phillip Bailey
QA Contact: Yihui Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-18 15:37 UTC by Ido Rosenzwig
Modified: 2018-04-02 11:04 UTC (History)
12 users (show)

Fixed In Version: cockpit-ovirt-0.11.18-0.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-29 11:12:55 UTC
oVirt Team: SLA
Embargoed:
rule-engine: ovirt-4.2+
ykaul: blocker+
rule-engine: testing_ack+


Attachments (Terms of Use)
no_error_appjs (299.99 KB, image/png)
2018-03-22 06:29 UTC, Yihui Zhao
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 89161 0 None MERGED wizard: move past exceptions 2020-04-15 14:37:23 UTC
oVirt gerrit 89163 0 master MERGED wizard: Make wizard init more robust 2020-04-15 14:37:23 UTC
oVirt gerrit 89203 0 ovirt-4.2 MERGED wizard: Make wizard init more robust 2020-04-15 14:37:23 UTC

Description Ido Rosenzwig 2018-03-18 15:37:26 UTC
Description of problem:
hosted-engine wizard is stuck on 'Loading wizard...' so the wizard is not opening.

This is the error on the web browser: 

uncaught (in promise) TypeError: Cannot read property 'plays' of null
    at e.value (app.js:25)
    at e.value (app.js:25)
    at t.value (app.js:25)
    at app.js:25
    at <anonymous>

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


How reproducible:
100%

Steps to Reproduce:
1. run hosted-engine deployment via cockpit
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Ido Rosenzwig 2018-03-19 07:32:07 UTC
cockpit-ovirt-dashboard-0.11.17-1.el7

Comment 3 Yihui Zhao 2018-03-20 05:41:40 UTC
I cannot reproduce this issue with cockpit-ovirt-dashboard-0.11.17-1.el7

hosted-engine wizard is not stuck on 'Loading wizard...'
But from the javascript console, find this:

SyntaxError: Unexpected end of JSON input
    at JSON.parse (<anonymous>)
    at app.js:25
    at Array.forEach (<anonymous>)
    at e.value (app.js:25)
    at app.js:25
    at new Promise (<anonymous>)
    at e.value (app.js:25)
    at app.js:25
    at <anonymous>


I saw the patch merged, if the fixed build coming, could you help to verify this bug about "Loading wizard..." stuck.

Comment 4 Phillip Bailey 2018-03-21 11:28:46 UTC
(In reply to Yihui Zhao from comment #3)

> SyntaxError: Unexpected end of JSON input
>     at JSON.parse (<anonymous>)
>     at app.js:25
>     at Array.forEach (<anonymous>)
>     at e.value (app.js:25)
>     at app.js:25
>     at new Promise (<anonymous>)
>     at e.value (app.js:25)
>     at app.js:25
>     at <anonymous>

This issue doesn't affect the loading process, but a patch [1] to fix it has been merged already, so it will go away in the next build, as well.

[1] https://gerrit.ovirt.org/#/c/89229/

Comment 5 Yihui Zhao 2018-03-22 06:29:10 UTC
Created attachment 1411620 [details]
no_error_appjs

Comment 6 Yihui Zhao 2018-03-22 06:33:55 UTC
From Comment 4, this issue doesn't affect the loading process.

Tested with cockpit-ovirt-dashboard-0.11.18-1.el7ev.noarch, cannot meet this issue, see attachment 1411620 [details], from the javascript console, it seems ok.

Javascript console:

General system data retrieval started.
Get network interfaces started.
No gdeploy answer files found.
Get network interfaces completed successfully.
Network interfaces retrieved successfully
General system data retrieved successfully.



So, change this bug's status to verified.

Comment 7 Sandro Bonazzola 2018-03-29 11:12:55 UTC
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.


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