Bug 1006844 - Jump to plugin tab via TUI up error
Jump to plugin tab via TUI up error
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: rc
: 6.5
Assigned To: Fabian Deutsch
Virtualization Bugs
: TestOnly
Depends On: 974673 994825
  Show dependency treegraph
Reported: 2013-09-11 07:27 EDT by Artyom
Modified: 2014-01-21 14:49 EST (History)
17 users (show)

See Also:
Fixed In Version: ovirt-node-3.0.1-5.el6
Doc Type: Bug Fix
Doc Text:
When entering the TUI of a hypervisor and attempting to move to the tab 'Plugins', an error appeared in the UI: "IndexError('list index out of range',) Press ENTER to logout ...or enter 's' to drop to shell" The system now continues to the TUI on the plugins tab without any error.
Story Points: ---
Clone Of:
Last Closed: 2014-01-21 14:49:43 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Artyom 2013-09-11 07:27:27 EDT
Description of problem:
Enter to TUI of rhevh and go to tab Plugins

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

How reproducible:

Steps to Reproduce:
1. see above

Actual results:
An error appeared in the UI: IndexError('list index out of range',)
Press ENTER to logout ...
or enter 's' to drop to shell

Expected results:
TUI on plugins tab without any error

Additional info:
Comment 1 Mike Burns 2013-09-11 07:37:24 EDT
known issue upstream, will be fixed with ovirt-node-3.0.1 backport
Comment 3 RHEL Product and Program Management 2013-10-13 22:15:10 EDT
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 5 Cheryn Tan 2013-11-07 19:32:50 EST
This bug is currently attached to errata RHBA-2013:15277. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:


Thanks in advance.
Comment 6 Charlie 2013-11-27 22:01:15 EST
Hiya, quick query, has this been fixed? Also could you let me know what was causing it?
Comment 7 Fabian Deutsch 2013-11-29 04:33:13 EST
Hey Charlie,

yep this has been fixed.
Comment 10 errata-xmlrpc 2014-01-21 14:49:43 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

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


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