Bug 1015013 - [RHSC] - Brick advanced details gives error.
Summary: [RHSC] - Brick advanced details gives error.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhsc
Version: 2.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: RHGS 2.1.2
Assignee: Darshan
QA Contact: RamaKasturi
URL:
Whiteboard:
Depends On:
Blocks: 1058203
TreeView+ depends on / blocked
 
Reported: 2013-10-03 10:01 UTC by RamaKasturi
Modified: 2015-05-13 16:33 UTC (History)
8 users (show)

Fixed In Version: CB6
Doc Type: Bug Fix
Doc Text:
Previously, an error was displayed whenever there was data overflow in few fields of Advanced Details window. Now, with this update, the datatype for those fields are modified to avoid the data overflow.
Clone Of:
: 1058203 (view as bug list)
Environment:
Last Closed: 2014-02-25 07:46:54 UTC
Embargoed:


Attachments (Terms of Use)
Attaching engine log (98.90 KB, text/x-log)
2013-10-03 10:02 UTC, RamaKasturi
no flags Details
Attaching screenshot for the same. (220.10 KB, image/png)
2013-11-08 09:26 UTC, RamaKasturi
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2014:0208 0 normal SHIPPED_LIVE Red Hat Storage 2.1 enhancement and bug fix update #2 2014-02-25 12:20:30 UTC
oVirt gerrit 20436 0 None None None Never

Description RamaKasturi 2013-10-03 10:01:43 UTC
Description of problem:
Brick advanced details gives error.

Version-Release number of selected component (if applicable):
rhsc-2.1.1-0.0.2.master.el6ev.noarch

How reproducible:
Always.

Steps to Reproduce:
1. Create a volume.
2. start the volume.
3. Go to the bricks subtab and select the brick.
4. Now click on the advanced details.


Actual results:
It opens a popup called Brick Details with error "Error in fetching brick details, please try again".

Expected results:
It should display advanced details of bricks.

Additional info:

Comment 1 RamaKasturi 2013-10-03 10:02:53 UTC
Created attachment 807000 [details]
Attaching engine log

Comment 2 RamaKasturi 2013-10-03 10:04:50 UTC
The following is what i see in engine logs.

013-10-03 20:57:53,589 ERROR [org.ovirt.engine.core.vdsbroker.gluster.GetGlusterVolumeAdvancedDetailsVDSCommand] (ajp-/127.0.0.1:8702-6) Failed in GetGlusterVolumeAdvancedDetailsVDS method, for vds: server1; host: 10.70.37.80
2013-10-03 20:57:53,590 ERROR [org.ovirt.engine.core.vdsbroker.gluster.GetGlusterVolumeAdvancedDetailsVDSCommand] (ajp-/127.0.0.1:8702-6) Command GetGlusterVolumeAdvancedDetailsVDS execution failed. Exception: NumberFormatException: For 
input string: "24138684608"
2013-10-03 20:57:53,590 INFO  [org.ovirt.engine.core.vdsbroker.gluster.GetGlusterVolumeAdvancedDetailsVDSCommand] (ajp-/127.0.0.1:8702-6) FINISH, GetGlusterVolumeAdvancedDetailsVDSCommand, log id: 57522167
2013-10-03 20:57:53,590 ERROR [org.ovirt.engine.core.bll.gluster.GetGlusterVolumeAdvancedDetailsQuery] (ajp-/127.0.0.1:8702-6) Query GetGlusterVolumeAdvancedDetailsQuery failed. Exception message is VdcBLLException: java.lang.NumberForma
tException: For input string: "24138684608" (Failed with error ENGINE and code 5001)
2013-10-03 20:57:53,912 INFO  [org.ovirt.engine.core.vdsbroker.gluster.GlusterServersListVDSCommand] (DefaultQuartzScheduler_Worker-26) START, GlusterServersListVDSCommand(HostName = server4, HostId = 28e7173e-52a0-4213-afce-6cd6221fb2b1
), log id: 752f5c1a

Comment 4 RamaKasturi 2013-10-09 11:18:36 UTC
Advanced deatils gives error after rebalance is run on the volume.

Comment 5 RamaKasturi 2013-10-18 10:36:46 UTC
Here is what comes in the logs:


2013-10-18 21:25:24,343 INFO [org.ovirt.engine.core.vdsbroker.gluster.GetGlusterVolumeAdvancedDetailsVDSCommand] (ajp-/127.0.0.1:8702-8) START, GetGlusterVolumeAdvancedDetailsVDSCommand(HostName = server2, HostId = cfccd3bf-8a6c-4b11-83c3-34db3b2a5b95), log id: 375e085
2013-10-18 21:25:25,200 ERROR [org.ovirt.engine.core.vdsbroker.gluster.GetGlusterVolumeAdvancedDetailsVDSCommand] (ajp-/127.0.0.1:8702-8) Failed in GetGlusterVolumeAdvancedDetailsVDS method, for vds: server2; host: 10.70.37.61
2013-10-18 21:25:25,200 ERROR [org.ovirt.engine.core.vdsbroker.gluster.GetGlusterVolumeAdvancedDetailsVDSCommand] (ajp-/127.0.0.1:8702-8) Command GetGlusterVolumeAdvancedDetailsVDS execution failed. Exception: NumberFormatException: For input string: "26237732000"
2013-10-18 21:25:25,200 INFO [org.ovirt.engine.core.vdsbroker.gluster.GetGlusterVolumeAdvancedDetailsVDSCommand] (ajp-/127.0.0.1:8702-8) FINISH, GetGlusterVolumeAdvancedDetailsVDSCommand, log id: 375e085
2013-10-18 21:25:25,200 ERROR [org.ovirt.engine.core.bll.gluster.GetGlusterVolumeAdvancedDetailsQuery] (ajp-/127.0.0.1:8702-8) Query GetGlusterVolumeAdvancedDetailsQuery failed. Exception message is VdcBLLException: java.lang.NumberFormatException: For input string: "26237732000" (Failed with error ENGINE and code 5001)




[root@localhost ~]# vdsClient -s 0 glusterVolumeStatus volumeName=vol_dis brick=10.70.37.61:/rhs/brick1/b2 option=clients
{'status': {'code': 0, 'message': 'Done'},
 'volumeStatus': {'bricks': [{'brick': '10.70.37.61:/rhs/brick1/b2',
                              'clientsStatus': [{'bytesRead': '26237732000',
                                                 'bytesWrite': '48139824',
                                                 'hostname': '10.70.37.185:1007'},
                                                {'bytesRead': '804',
                                                 'bytesWrite': '616',
                                                 'hostname': '10.70.37.185:1018'},
                                                {'bytesRead': '1572',
                                                 'bytesWrite': '1264',
                                                 'hostname': '10.70.37.61:1010'},
                                                {'bytesRead': '1244',
                                                 'bytesWrite': '940',
                                                 'hostname': '10.70.37.166:1008'},
                                                {'bytesRead': '1248',
                                                 'bytesWrite': '940',
                                                 'hostname': '10.70.37.167:993'},
                                                {'bytesRead': '1244',
                                                 'bytesWrite': '940',
                                                 'hostname': '10.70.37.69:989'}]}],
                  'name': 'vol_dis'}}

Comment 6 Darshan 2013-10-21 09:57:47 UTC
can you attach the vdsm logs.

Comment 7 RamaKasturi 2013-11-08 09:26:11 UTC
Created attachment 821461 [details]
Attaching screenshot for the same.

Comment 8 RamaKasturi 2013-11-08 09:27:03 UTC
Verified in cb6.(rhsc-2.1.2-0.22.master.el6_4.noarch) and this works fine.

Comment 9 Shalaka 2014-01-03 11:20:50 UTC
Please review the edited DocText and confirm.

Comment 10 Darshan 2014-01-03 11:56:50 UTC
(In reply to Shalaka from comment #9)
> Please review the edited DocText and confirm.
Looks good.

Comment 12 errata-xmlrpc 2014-02-25 07:46:54 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.

http://rhn.redhat.com/errata/RHEA-2014-0208.html


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