Bug 1211347 - UI reports "Cluster Updates Are Stale. The Cluster isn't updating Calamari. Please contact Administrator" when client clock is skewed more than 15min
Summary: UI reports "Cluster Updates Are Stale. The Cluster isn't updating Calamari. P...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Documentation
Version: 1.2.3
Hardware: All
OS: All
unspecified
medium
Target Milestone: rc
: 1.3.1
Assignee: ceph-docs@redhat.com
QA Contact: ceph-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-13 17:06 UTC by Christina Meno
Modified: 2015-12-18 09:59 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-18 09:59:11 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 11379 0 None None None Never

Description Christina Meno 2015-04-13 17:06:14 UTC
How reproducible: 100%


Steps to Reproduce:
1. set client clock to be 20min slow or fast relative to atomic time.
2. visit calamari dashboard
3. observe yellow error bar across top: "Cluster Updates Are Stale. The Cluster isn't updating Calamari. Please contact Administrator"

Actual results: Error when cluster state is being updated


Expected results: No error

Comment 1 Christina Meno 2015-04-13 17:06:40 UTC
http://tracker.ceph.com/issues/11379

Comment 2 Federico Lucifredi 2015-07-11 00:00:04 UTC
I believe we require the whole cluster to be NTP-synchronized, so I lean towards CLOSED/NOTABUG, unless Gregory thinks a better error message is possible.

Comment 3 Christina Meno 2015-07-14 18:34:42 UTC
Going to add NTP to admin node in docs

Comment 7 John Wilkins 2015-09-29 18:05:06 UTC
Will stage soon.

Comment 9 Tamil 2015-10-10 00:41:08 UTC
verified on 1.3. 
no doc link for 1.2.3

Comment 10 Nilamdyuti 2015-10-12 09:48:01 UTC
(In reply to Tamil from comment #9)
> verified on 1.3. 
> no doc link for 1.2.3

John made the changes to 1.3 doc and not in 1.2.3 doc. So, the resolution is made in 1.3 only.

Comment 11 Anjana Suparna Sriram 2015-12-18 09:59:11 UTC
Fixed for 1.3.1 Release.


Note You need to log in before you can comment on or make changes to this bug.