Bug 1034437 - [RHSC] Adding Host - Error while executing action: A Request to the Server failed
Summary: [RHSC] Adding Host - Error while executing action: A Request to the Server fa...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhsc
Version: 2.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: RHGS 3.0.3
Assignee: Sahina Bose
QA Contact: Shruti Sampat
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-25 20:22 UTC by Matt Mahoney
Modified: 2015-05-13 17:41 UTC (History)
10 users (show)

Fixed In Version: rhsc-3.0.2-1.16.el6rhs.noarch.rpm
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-01-15 13:47:22 UTC
Embargoed:


Attachments (Terms of Use)
Engine log (312.44 KB, text/plain)
2013-11-25 20:24 UTC, Matt Mahoney
no flags Details
Error dialog (224.64 KB, image/png)
2013-11-25 20:24 UTC, Matt Mahoney
no flags Details
server logs (244.52 KB, text/x-log)
2013-12-09 11:15 UTC, Shruti Sampat
no flags Details
engine logs (9.10 MB, text/x-log)
2013-12-09 11:19 UTC, Shruti Sampat
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0039 0 normal SHIPPED_LIVE Red Hat Storage Console 3.0 enhancement and bug fix update #3 2015-01-15 18:46:40 UTC

Description Matt Mahoney 2013-11-25 20:22:51 UTC
Description of problem:
The following error dialog appeared when adding a host (via automation run:

"	
Error while executing action: A Request to the Server failed: java.lang.reflect.InvocationTargetException"

Closing the error dialog, and the adding the host again was successful.

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

How reproducible:
Intermittent

Steps to Reproduce:
1. Create a cluster
2. Add a host
3.

Actual results:


Expected results:
Should not experience an error dialog when adding a host.

Additional info:

Comment 1 Matt Mahoney 2013-11-25 20:24:03 UTC
Created attachment 828871 [details]
Engine log

Comment 2 Matt Mahoney 2013-11-25 20:24:31 UTC
Created attachment 828872 [details]
Error dialog

Comment 4 Sahina Bose 2013-11-28 10:34:49 UTC
Please provide server.log when the exception happens.

Comment 5 Shruti Sampat 2013-12-09 11:14:24 UTC
Saw this issue with Red Hat Storage Console Version: 2.1.2-0.26.master.el6_5. Find server.log attached.

Comment 6 Shruti Sampat 2013-12-09 11:15:56 UTC
Created attachment 834304 [details]
server logs

Comment 7 Shruti Sampat 2013-12-09 11:19:11 UTC
Created attachment 834305 [details]
engine logs

Comment 8 Sahina Bose 2013-12-12 12:50:20 UTC
Could not reproduce this error. The only error in server.log was related to connection to the AD server, and this is not related to the exception in the UI.

If you can, please provide exact steps to reproduce.

Comment 9 Shruti Sampat 2013-12-13 07:02:53 UTC
I have not observed any kind of consistent pattern or specific steps that may have led to this issue.

Comment 10 Kanagaraj 2013-12-13 13:46:53 UTC
RHEVM Bug - bz#1039248

Comment 11 Sahina Bose 2013-12-19 05:46:00 UTC
Since this bug is intermittent in nature without reproducible steps, taking it out of Corbett release

Comment 12 Sahina Bose 2014-09-03 15:10:56 UTC
The related RHEV-M Bug 1039248 mentions GWT serialization issues as cause for this issue and fixed with introduction of no-arg constructors in all entity classes.

As part of rebase with oVirt 3.4, the issue can be closed. Needs to be verified.

Comment 14 Shruti Sampat 2014-11-19 10:37:53 UTC
Have not seen this issue with recent builds (I am testing on rhsc-3.0.3-1.17.el6rhs.noarch). Marking as verified.

Comment 16 errata-xmlrpc 2015-01-15 13:47:22 UTC
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.

https://rhn.redhat.com/errata/RHBA-2015-0039.html


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