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:
Verified in bb5 build.
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