Bug #7399: HEALTH WARNING loops forever - teuthology - Ceph

Actions

Copy link

Bug #7399

closed

HEALTH WARNING loops forever

Added by Anonymous about 10 years ago. Updated about 10 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Category:

% Done:

Source:

other

Tags:

Backport:

Regression:

Severity:

3 - minor

Reviewed:

Affected Versions:

ceph-qa-suite:

Crash signature (v1):

Crash signature (v2):

Description

I keep getting the following message on teuthology:

DEBUG:teuthology.orchestra.run:Running [10.214.131.108]: 'adjust-ulimits ceph-coverage /home/ubuntu/cephtest/archive/coverage ceph health'
DEBUG:teuthology.misc:Ceph health: HEALTH_WARN crush map has non-optimal tunables
DEBUG:teuthology.orchestra.run:Running [10.214.131.108]: 'adjust-ulimits ceph-coverage /home/ubuntu/cephtest/archive/coverage ceph health'
DEBUG:teuthology.misc:Ceph health: HEALTH_WARN crush map has non-optimal tunables

Actions

Copy link

Updated by Anonymous about 10 years ago

The following is the yaml file that produces this problem:

roles:
- [mon.a, mon.c, osd.0, osd.1, osd.2, client.0]
- [mon.b, mds.a, osd.3, osd.4, osd.5, client.1]
overrides:
  ceph:
    fs: ext4
tasks:
- clock:
- install:
- ceph:
- rgw: [client.0]
- workunit:
    clients:
      client.0:
        - rgw/s3_multipart_upload.pl
targets:
  ubuntu@mira016.front.sepia.ceph.com: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC2iFtbgXmASSSyx4bED72JOI6s982oSB7FW43+fOsshNeytF4zGLiV52Y4C3DgAiVA/VsT84JEsVhTFMCOfBIEGMY7JlIbKjI/2dw426cHHkTwQhu9eqYqXaLe8EyN8SkJ/cNw86cQ5xHnflzdQuzbs5gbRC7wRLZq2me9lFIqnQAkZDl8K/MMze63CeVgQe8XBsUA5qzFvLpAdmLn12QyoCZRfbFIz5bXHhYx/XJI4OXw9wPwHNIFrBc/twdpDVkd8cFhVaKYeePjr8eQQNiJETnR6AsAy1nGd0pZ6aPTPFYd62AOVuwl0OmlcHTM4YDva4Xb8gFHF6rj8UnsXSyd
  ubuntu@mira032.front.sepia.ceph.com: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDY2fnqu6A9D9/cCymfUS+B3rEsFSDOGWqarcRKLY64qqHRlow/S4u2Ev3qI8y2bfl8yu/WH8TqR+Btm/W+dV6qnoPO5zLtuiJ8WMoYYyfMnUkUzgkBSq88lqfeyJFhdpRSAfEye5ms0q1v6qp0PzPfB/W5srGnQHYryvroWif7uOsjpjmKCZ4VStmz8EG5cvybmSXtA8AEHMcJqN2Kx1DTNgo+E+cITRwbJ7V8RUwP5eBS/0mEPIJ4udqQQvqRegyNR0dNeH0fTLPDTQe+SVyHsvR3emkOt7pJ9mVvavvqZwAxH2t+1S7K2RDdl5outKr+DgZ7vLhnRYhwjFek+kD3

Actions

Copy link

Updated by Anonymous about 10 years ago

Note that this setup was merrily chugging along (but failing), before it fell into this loop.

Actions

Copy link

Updated by Sage Weil about 10 years ago

what version is this? this error will definitely come up on the upgrade tests (been waiting for that to happen to confirm they are working) but it shouldn't happen on a cluster that doesn't change versions.

Actions

Copy link