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 1360819 - Make the root cause of RHEV deployment errors more apparent in the UI
Summary: Make the root cause of RHEV deployment errors more apparent in the UI
Status: NEW
Alias: None
Product: Red Hat Quickstart Cloud Installer
Classification: Red Hat
Component: Installation - RHEV
Version: 1.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: John Matthews
QA Contact: Dave Johnson
Dan Macpherson
Depends On:
TreeView+ depends on / blocked
Reported: 2016-07-27 14:59 UTC by James Olin Oden
Modified: 2016-09-27 22:49 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)

Description James Olin Oden 2016-07-27 14:59:15 UTC
Description of problem:
In my case I was installing with too little memory for a self hosted deployment but the error I received on the UI was:

====== Puppet run for mac52540055edf8.b.b puppet run reported as out of sync for the last 10 polls - something may have gone wrong. ====== 

As it turned out in the vdsm.log file on the RHEV host, there were errors like this:

Thread-170276::ERROR::2016-07-27 14:02:32,825::dispatcher::79::Storage.Dispatcher::(wrapper) list index out of range
Traceback (most recent call last):
  File "/usr/share/vdsm/storage/", line 71, in wrapper
    result = ctask.prepare(func, *args, **kwargs)
  File "/usr/share/vdsm/storage/", line 104, in wrapper
    return m(self, *a, **kw)
  File "/usr/share/vdsm/storage/", line 1179, in prepare
    raise self.error
IndexError: list index out of range

That being from the storage subsystem indicated some sort of storage problem, and since tmp needs to be bigger I knew that I didn't have enough memory.  However, a similar problem in the field could take a bit longer to diagnose, and in general, errors that happen on the RHEV system as its being deployed are not visible from the QCI UI.   So having some way to gather useful logs and make them accessible from the UI would be really helpful.

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

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

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