Bug 1464964

Summary:	[RFE]: Avoid raising spurious health warnings during initial setup of cluster
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	John Spray <john.spray>
Component:	RADOS	Assignee:	Josh Durgin <jdurgin>
Status:	CLOSED ERRATA	QA Contact:	shylesh <shmohan>
Severity:	urgent	Docs Contact:	Erin Donnelly <edonnell>
Priority:	urgent
Version:	3.0	CC:	anharris, ceph-eng-bugs, dzafman, edonnell, hnallurv, icolle, jdurgin, john.spray, kchai, kdreyer
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	RHEL: ceph-12.2.0-1.el7cp Ubuntu: ceph_12.2.0-2redhat1xenial	Doc Type:	Bug Fix
Doc Text:	.New health checks with more structure Previously, during the installation of a Red Hat Ceph Storage cluster, Ceph raised spurious health warnings. The health checks have been improved to be more structured and no longer trigger health warnings on healthy clusters.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-05 23:34:34 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:	1494421

Description John Spray 2017-06-26 10:07:19 UTC

Historically we have sometimes had health warnings for things like too few OSDs, PGs, PGs in peering/creating state, that would appear even on a perfectly healthy system while it was being set up.

Normal set up of a Ceph cluster should not trigger any health warnings or log messages at WRN or ERR.

Comment 4 Josh Durgin 2017-08-30 17:44:36 UTC

https://github.com/ceph/ceph/pull/15643

Comment 7 John Spray 2017-09-27 14:35:04 UTC

You also need to check the cluster log for WARN or ERROR messages.

Comment 9 John Spray 2017-09-28 08:28:23 UTC

Yes, if there are no warnings or errors, you're good to go.

Comment 10 shylesh 2017-09-28 08:57:39 UTC

Verified on 12.2.0-3redhat1xenial

Comment 15 errata-xmlrpc 2017-12-05 23:34:34 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/RHBA-2017:3387