Bug 1464964 - [RFE]: Avoid raising spurious health warnings during initial setup of cluster
[RFE]: Avoid raising spurious health warnings during initial setup of cluster
Product: Red Hat Ceph Storage
Classification: Red Hat
Component: RADOS (Show other bugs)
Unspecified Unspecified
urgent Severity urgent
: rc
: 3.0
Assigned To: Josh Durgin
Erin Donnelly
: FutureFeature
Depends On:
Blocks: 1494421
  Show dependency treegraph
Reported: 2017-06-26 06:07 EDT by John Spray
Modified: 2017-12-05 18:34 EST (History)
10 users (show)

See Also:
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:
Last Closed: 2017-12-05 18:34:34 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Github ceph/ceph/pull/15643 None None None 2017-08-30 14:36 EDT

  None (edit)
Description John Spray 2017-06-26 06:07:19 EDT
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 13:44:36 EDT
Comment 7 John Spray 2017-09-27 10:35:04 EDT
You also need to check the cluster log for WARN or ERROR messages.
Comment 9 John Spray 2017-09-28 04:28:23 EDT
Yes, if there are no warnings or errors, you're good to go.
Comment 10 shylesh 2017-09-28 04:57:39 EDT
Verified on 12.2.0-3redhat1xenial
Comment 15 errata-xmlrpc 2017-12-05 18:34:34 EST
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.


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