Bug 1340142

Summary:	syncing cluster state
Product:	[Red Hat Storage] Red Hat Storage Console	Reporter:	Lubos Trilety <ltrilety>
Component:	unclassified	Assignee:	Shubhendu Tripathi <shtripat>
Status:	CLOSED ERRATA	QA Contact:	Lubos Trilety <ltrilety>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	2	CC:	mkudlej, nthomas, sankarshan
Target Milestone:	---
Target Release:	2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rhscon-core-0.0.26-1.el7scon.x86_64	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-08-23 19:52:21 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1344195

Description Lubos Trilety 2016-05-26 14:02:00 UTC

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):
rhscon-core-0.0.19-1.el7scon.x86_64
rhscon-ceph-0.0.18-1.el7scon.x86_64
rhscon-ui-0.0.34-1.el7scon.noarch

How reproducible:
100%

Steps to Reproduce:
1. Create some cluster
2. Restart skyring service
3.

Actual results:
Cluster has a syncing state. Pool cannot be created because it says that cluster is not active.


Expected results:
Cluster state will change after some time to failed/warning/ok

Additional info:

Comment 1 Shubhendu Tripathi 2016-06-07 05:03:15 UTC

@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.

Comment 2 Lubos Trilety 2016-08-03 09:09:07 UTC

We don't see that in last several weeks.
The latest build which we use:
rhscon-core-0.0.38-1.el7scon.x86_64
rhscon-ceph-0.0.38-1.el7scon.x86_64
rhscon-core-selinux-0.0.38-1.el7scon.noarch
rhscon-ui-0.0.51-1.el7scon.noarch

If the issue appears again the BZ will be re-opened.

Comment 4 errata-xmlrpc 2016-08-23 19:52:21 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.

https://access.redhat.com/errata/RHEA-2016:1754