Bug 915675

Summary: Gluster volume is stopped, but brick status on the UI is still 'UP'
Product: Red Hat Enterprise Virtualization Manager Reporter: Shruti Sampat <ssampat>
Component: ovirt-engine-webadmin-portalAssignee: Shireesh <shireesh>
Status: CLOSED ERRATA QA Contact: Shruti Sampat <ssampat>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.2.0CC: acathrow, dtsang, dyasny, ecohen, iheim, knarra, mmahoney, pprakash, Rhev-m-bugs, sabose, scohen, sdharane, shtripat, ykaul
Target Milestone: ---   
Target Release: 3.2.0   
Hardware: All   
OS: All   
Whiteboard: gluster
Fixed In Version: Doc Type: Bug Fix
Doc Text:
--no tech note required
 Story Points: ---
Clone Of: Environment:
Last Closed: 2013-06-10 21:34:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Gluster RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
engine logs
none
vdsm logs - server 1
none
vdsm logs - server 2 none

Description Shruti Sampat 2013-02-26 10:10:12 UTC 
Description of problem:
---------------------------------------
For a volume that was started and then stopped from the gluster CLI, the brick status still remained 'UP', even after the volume was stopped. The volume status shows the correct status, i.e. DOWN.

Version-Release number of selected component (if applicable):
Red Hat Enterprise Virtualization Manager Version: 3.2.0-8.el6ev 

How reproducible:
Intermittent

Steps to Reproduce:
1. Create a volume from gluster CLI
2. Start the volume and then stop the volume within a couple of minutes.
  
Actual results:
The brick status incorrectly reports UP after the volume is stopped.

Expected results:
The brick status should say DOWN after the volume is stopped.

Additional info:
Comment 1 Shruti Sampat 2013-02-26 10:40:01 UTC 
Created attachment 702775 [details]
engine logs
Comment 2 Shruti Sampat 2013-02-26 10:41:24 UTC 
Created attachment 702777 [details]
vdsm logs - server 1
Comment 3 Shruti Sampat 2013-02-26 11:25:59 UTC 
Created attachment 702798 [details]
vdsm logs - server 2
Comment 5 Shruti Sampat 2013-04-01 14:28:09 UTC 
Verfified as fixed in Red Hat Enterprise Virtualization Manager Version: 3.2.0-10.17.master.el6ev.
Comment 6 Cheryn Tan 2013-04-03 06:51:23 UTC 
This bug is currently attached to errata RHEA-2013:14491. 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:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes

Thanks in advance.
Comment 7 errata-xmlrpc 2013-06-10 21:34:05 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/RHSA-2013-0888.html