Red Hat Bugzilla – Bug 980750
[RHSC] When a host is moved to Maintenance after being Non-operational, it is removed from the cluster, if another host in the cluster is UP.
Last modified: 2015-05-13 12:34:21 EDT
Description of problem:
When a host in a cluster is UP, and another is added, if it ends up in Non-Operational state, the only way to reinstall that node is to move it to Maintenance and then reinstall. But after it is moved to Maintenance, the host is removed from the cluster.
Version-Release number of selected component (if applicable):
Red Hat Storage Console Version: 2.1.0-0.bb4.el6rhs
Steps to Reproduce:
1. Add a host to a cluster via the Console, let it come UP.
2. Add another host, such that it ends up in Non-operational state. (could be due to absence of glusterfs packages)
3. Move the Non-operational host to Maintenance, inorder to reinstall.
Host is removed from the cluster.
The engine should allow a reinstall of the host after being moved to Maintenance.
Verified CB6. Have not encountered this issue. Setting as Validated, and will reopen if it is seen again.
Please review the edited DocText and confirm.
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.