This reverts 693bd23851, which was
added in response to http://tracker.ceph.com/issues/18126. But
we updated the Ubuntu packages in sepia so it should be good to go.
Signed-off-by: Greg Farnum <gfarnum@redhat.com>
Set pool size back to 2 so we don't have to have backfill
complete (despite rejection probability) in order to get back to
healthy. This way we scrub on cleanup.
Signed-off-by: Sage Weil <sage@redhat.com>
If we leave the quota set, the proxied ops will block
indefinitely, which will block scrubbing on the cache tier pgs
indefinitely.
Signed-off-by: Sage Weil <sage@redhat.com>
This reverts commit be88220965.
we can workaround the limit of old requests by using the backward
compatible way.
Signed-off-by: Kefu Chai <kchai@redhat.com>
This reverts 693bd23851, which was
added in response to http://tracker.ceph.com/issues/18126. But
we updated the Ubuntu packages in sepia so it should be good to go.
Signed-off-by: Greg Farnum <gfarnum@redhat.com>
- OSDMap encode and decode translate between the flags and int
representations.
- OSDMap::Incremental only does decode; we do not expect to ever encode
an incremental osdmap for an old osd that sets any of these flags.
- the 'osd set' command still lets you set the jewel and kraken flags,
but not luminous.
- OSDMap::apply_incremental handles the conversion of legacy require flags
to the new field if the jewel or kraken flags have to be set before
starting the osd upgrade.
- clear out the legacy flags when we make the luminous transition only;
until then we keep using the old flag in the encoded and decoded version
(although the require_osd_release field will be accurate in memory in all
cases).
Signed-off-by: Sage Weil <sage@redhat.com>
This parsed out as
tasks:
- install: null
- ceph:
conf:
osd: osd max object name len = 400 osd max object namespace len = 64
- workunit:
clients:
all:
- rados/test_health_warnings.sh
which is clearly not correct.
Signed-off-by: Sage Weil <sage@redhat.com>
The scrub_pgs command also waits for healthy for a while, but fails
silently if it times out, which means the subsequent scrubs will also
fail to clean up.
This forces an earlier failure that does not obscure the root cause.
Signed-off-by: Sage Weil <sage@redhat.com>
We don't want to do the at-end.yaml scrubbing business with this test.
Move it into a separate collection until after luminous.
I have a todo item on the post-luminous cleanup list to avoid forgetting
to move this back.
Fixes: http://tracker.ceph.com/issues/19935
Signed-off-by: Sage Weil <sage@redhat.com>
The OSDs must have a map reflecting the require_luminous flag in order
for the legacy conversion to happen. A quick rados bench should ensure
that.
Signed-off-by: Sage Weil <sage@redhat.com>
This lets us run multiple cleanup steps right before ceph
teardown.
Note that we drop the facet from multimon/ because it
doesn't factor out cluster creation before this step
properly. That's fine because the require_luminous
cleanup shouldn't be related to the multimon tests.
Signed-off-by: Sage Weil <sage@redhat.com>
