Description of problem: Create Volume shows error "No host found in 'UP' state in the cluster, please select another cluster."even though the hosts are UP Version-Release number of selected component (if applicable): rhsc-2.1-0.qa4d.el6rhs How reproducible: 100% Steps to Reproduce: 1. From the Tree view on the LHS, select a cluster having some hosts in UP state. 2. Click on the "Servers" tab under that cluster and do confirm that the hosts are actually in the UP state. 3. Now, select "volumes" tab under "Servers" and click on "Create Volume". 4. In that dialogue window, you will see the error "No host found in 'UP' state in the cluster, please select another cluster." on the bottom of that window. Actual results: Error message is displayed even though the hosts are in UP state. Expected results: It shouldn't display the error when the hosts in a cluster are in UP state. Additional info: Screenshots are attached for references. a.) Note that even though it says, no hosts are in UP state, the "Add Bricks" tab is still not disabled and hence volume creation is still successful. In fact, it should succeed as the hosts are actually UP. So looks like a wrong validation when the "Create Volume" operation is done from the "Tree" view.
Created attachment 684069 [details] screenshot of error
Created attachment 684071 [details] screenshot showing that the Hosts are actually in UP state
Created attachment 684072 [details] screenshot showing that the Add Bricks field is enabled and volume creation is successful
Engine and vdsm logs please.
Created attachment 684126 [details] Engine logs
Created attachment 684127 [details] Vdsm logs from Host1
Created attachment 684128 [details] Vdsm logs from Host2
fixed in upstream: http://gerrit.ovirt.org/10744
verified as fixed in 2.1.0-0.qa5.el6rhs
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