Description of problem:
After some time cluster state is switched to syncing (state: 4 in mongodb) and it never changes back to some proper state.
There's this line in skyring.log:
sync.go:60 SyncClusterDetails] skyring:1e27f6b9-f1a9-4ce4-9149-3265e2126654-Cluster ceph is not in active state. Skipping sync.
But the cluster is active. When the state is changed manually in mongodb everything seems to work. Pools can be created etc.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create some cluster
2. Restart skyring service
Cluster has a syncing state. Pool cannot be created because it says that cluster is not active.
Cluster state will change after some time to failed/warning/ok
@Lubos, is it like cluster remains in syncing state forever. I dont think so. I am having patch https://review.gerrithub.io/#/c/279279/ to make sure cluster is moved back to active state, if syncing fails at any stage.
Hope this would solve the issue.
We don't see that in last several weeks.
The latest build which we use:
If the issue appears again the BZ will be re-opened.
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.