Created attachment 662289 [details] engine logs Description of problem: --------------------------------------- When a brick that is part of a volume is brought down by killing the brick process, the brick status on the Console still shows 'UP'. The following is seen in the engine logs - --------------------------------------- 2012-12-12 09:46:01,420 INFO [org.ovirt.engine.core.vdsbroker.gluster.GetGlusterVolumeAdvancedDetailsVDSCommand] (QuartzScheduler_Worker-29) START, G etGlusterVolumeAdvancedDetailsVDSCommand(HostName = 10.70.35.13, HostId = 62b0de10-703f-4456-9dcc-174284ae996e), log id: 2c20be69 2012-12-12 09:46:01,563 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand] (QuartzScheduler_Worker-29) Failed in GetGlusterVolumeAdvan cedDetailsVDS method, for vds: 10.70.35.13; host: 10.70.35.13 2012-12-12 09:46:01,563 ERROR [org.ovirt.engine.core.vdsbroker.VDSCommandBase] (QuartzScheduler_Worker-29) Command GetGlusterVolumeAdvancedDetailsVDS execution failed. Exception: NumberFormatException: For input string: "N/A" 2012-12-12 09:46:01,563 INFO [org.ovirt.engine.core.vdsbroker.gluster.GetGlusterVolumeAdvancedDetailsVDSCommand] (QuartzScheduler_Worker-29) FINISH, GetGlusterVolumeAdvancedDetailsVDSCommand, log id: 2c20be69 2012-12-12 09:46:01,563 ERROR [org.ovirt.engine.core.bll.gluster.GlusterManager] (QuartzScheduler_Worker-29) Error while refreshing brick statuses for volume test of cluster cluster1: org.ovirt.engine.core.common.errors.VdcBLLException: VdcBLLException: java.lang.NumberFormatException: For input str ing: "N/A" at org.ovirt.engine.core.bll.VdsHandler.handleVdsResult(VdsHandler.java:214) [engine-bll.jar:] at org.ovirt.engine.core.bll.VDSBrokerFrontendImpl.RunVdsCommand(VDSBrokerFrontendImpl.java:33) [engine-bll.jar:] at org.ovirt.engine.core.bll.gluster.GlusterManager.runVdsCommand(GlusterManager.java:216) [engine-bll.jar:] at org.ovirt.engine.core.bll.gluster.GlusterManager.getVolumeAdvancedDetails(GlusterManager.java:823) [engine-bll.jar:] at org.ovirt.engine.core.bll.gluster.GlusterManager.refreshBrickStatuses(GlusterManager.java:796) [engine-bll.jar:] at org.ovirt.engine.core.bll.gluster.GlusterManager.refreshClusterHeavyWeightData(GlusterManager.java:783) [engine-bll.jar:] at org.ovirt.engine.core.bll.gluster.GlusterManager.refreshHeavyWeightData(GlusterManager.java:761) [engine-bll.jar:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_09-icedtea] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_09-icedtea] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_09-icedtea] at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_09-icedtea] at org.ovirt.engine.core.utils.timer.JobWrapper.execute(JobWrapper.java:60) [engine-scheduler.jar:] at org.quartz.core.JobRunShell.run(JobRunShell.java:213) [quartz-2.1.2.jar:] at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:557) [quartz-2.1.2.jar:] Version-Release number of selected component (if applicable): Red Hat Storage Console Version: 2.1-qa18.el6ev vdsm version: vdsm-4.9.6-32.0.qa3.el6rhs.x86_64 How reproducible: Always Steps to Reproduce: 1. Create a volume 2. Start the volume. 3. Kill one of the brick processes on the storage node. Actual results: The brick status on the Console continues to show 'UP' Expected results: The brick status should show 'DOWN' Additional info: Output of 'gluster volume status' command on the storage node is - --------------------------------------- [root@localhost ~]# gluster volume status Status of volume: test Gluster process Port Online Pid ------------------------------------------------------------------------------ Brick 10.70.35.13:/opt/gluster/bricks/testBrick N/A N N/A NFS Server on localhost 38467 Y 2778 NFS Server on 10.70.35.28 38467 Y 9682
Patch sent to upstream : http://gerrit.ovirt.org/#/c/10022/
Verfied in Red Hat Storage Console Version: 2.1-0.qa4d.el6rhs. Brick status on the Console now reflects the status of the brick correctly whenever it is brought down/up.
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/RHBA-2013-1262.html