Bug 975326 - [RHSC] - Swift status should go to unknown state for a non-responsive host.
Summary: [RHSC] - Swift status should go to unknown state for a non-responsive host.
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: ---
: ---
Assignee: Shubhendu Tripathi
QA Contact: RamaKasturi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-18 06:06 UTC by RamaKasturi
Modified: 2013-09-23 22:25 UTC (History)
7 users (show)

Fixed In Version: bb5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-23 22:25:49 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 15904 0 None None None Never

Description RamaKasturi 2013-06-18 06:06:14 UTC
Description of problem:
Swift status should be changed to UNKNOWN for a non responsive host.

Version-Release number of selected component (if applicable):
rhsc-2.1.0-0.bb3.el6rhs.noarch
vdsm-4.10.2-22.3.el6rhs.x86_64
glusterfs-3.4.0.9rhs-1.el6rhs.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Create a cluster with two nodes attached to it.
2. Make one of them to go to non responsive state by stopping the vdsm.
3. 

Actual results:
Swift status does not go to UNKNOWN state in the server.

Expected results:
Swift status should be changed to unknown in the server.

Additional info:

Comment 2 RamaKasturi 2013-07-08 11:27:54 UTC
Verified in bb5 build.

Comment 3 Scott Haines 2013-09-23 22:25:49 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/RHBA-2013-1262.html


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