Bug 782485
| Summary: | Exception on Inventory page after wallaby remove-node | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Chad Roberts <croberts> | ||||
| Component: | cumin | Assignee: | Chad Roberts <croberts> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Stanislav Graf <sgraf> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 2.1 | CC: | ltoscano, matt, mkudlej, sgraf, tmckay | ||||
| Target Milestone: | 2.1.1 | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | cumin-0.1.5192-1 | Doc Type: | Bug Fix | ||||
| Doc Text: |
Cause: Unhandled exception on inventory page when wallaby data was expected/possible but not present.
Consequence: Exception dump on Inventory page.
Fix: We now are properly handling the possible exception
Result: The inventory page now displays without error.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-02-06 18:19:17 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 765607 | ||||||
| Attachments: |
|
||||||
Updated steps to reproduce: Set up a system such that there is a mix of nodes in the inventory. Some of the nodes (at least 1) should be a wallaby node. At least one node should be a node that is only reporting sesame data (it doesn't even need to be running condor, just point its sesame.conf to the broker). Give cumin a minute or two to refresh the wallaby nodes and update the sesame data. After that, the Inventory page should fail with an exception. Fixed in revision 5187 on trunk.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Cause: Unhandled exception on inventory page when wallaby data was expected/possible but not present.
Consequence: Exception dump on Inventory page.
Fix: We now are properly handling the possible exception
Result: The inventory page now displays without error.
Reproducing:
RHEL5 x86_64, cumin-0.1.5184-1.el5.noarch
Mixed pool:
node1: condor+wallaby
node2: condor+sesame
Cumin on the 3rd machine.
Immediatelly when clicking on Inventory page I have error:
...
File "/usr/share/cumin/python/wooly/template.py", line 90, in render
result = frag(self.__object, session, *args)
File "/usr/share/cumin/python/wooly/table.py", line 249, in render_cell_title
return self.parent.render_cell_title(session, record)
File "/usr/share/cumin/python/cumin/inventory/system.py", line 409, in render_cell_title
return record[self.field.index]
IndexError: tuple index out of range
VERIFY: RHEL5 i386/x86_64 cumin-0.1.5192-1.el5 RHEL6 i386/x86_64 cumin-0.1.5192-1.el6 Setup host1 with condor+sesame (-wallaby) Setup host2 with condor+wallaby (-sesame) Point them to cumin host3 with condor+wallaby+sesame In previous version cumin crash. Now it displays host1 (sesame only) "Kernel/Architecture/Free Memory/Load average" host2 (wallaby only) "Tags/Last checkin" host3 (wallaby+sesame) all fields VERIFIED 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. http://rhn.redhat.com/errata/RHSA-2012-0100.html |
Created attachment 555812 [details] Exception from inventory page Description of problem: While on the cumin inventory page, perform a wallaby remove-node (outside of cumin). Hit refresh on the cumin inventory page and wind-up with an exception (see attachment) Version-Release number of selected component (if applicable): 2.1 How reproducible: Unsure, possibly timing related. Steps to Reproduce: 1. Go to the cumin inventory page 2. Outside of cumin, perform a wallaby remove-node action for one of the listed nodes on the inventory page. 3. Refresh the inventory page. Actual results: Application error (see attachment) Expected results: No application error