* rados cli prints "head" at seeing CEPH_NOSNAP, so update the test
accordingly
* print inconsistent objs before testing them
Fixes: #14924
Signed-off-by: Kefu Chai <kchai@redhat.com>
because the repair for digest mismatch will rewrite the omap digest
in the corresponding OI attribute with the one calculated from the
omap read from disk. this is fine. but the succeeding test can not
use the same way used before to mess up the victim object in hope
to get an inconsistent object, as we have accepted it as an authroized
copy and populate the change to its replicas. to address this
problem, the crime scene of the `test_repair_bad_omap()` is cleaned
up before calling `repair()`. it helps with isolating the different
tests, so new tests should not worry about what the current omap
should look like.
Signed-off-by: Kefu Chai <kchai@redhat.com>
Basically same thing as
c0b0ec2831
client is getting ENXIO when trying to do osd tell because
the osd isn't quite up yet.
Signed-off-by: Samuel Just <sjust@redhat.com>
Get some coverage on the otherwise rarely touched
injectargs and `config set` interfaces.
Fixes: #14365
Signed-off-by: John Spray <john.spray@redhat.com>
For tests that specifically want to exercise an
asok operation (the test is responsible for
verifying that its mount object really is a
FuseMount and not a KernelMount)
Signed-off-by: John Spray <john.spray@redhat.com>
Because volume client cues its PG counts from the
mon pg warn max per osd setting, the teuthology template's
ultra-high 10000 setting causes problems. Force it down
to the usual sensible default for this test.
Also update vstart_runner to populate ctx.daemons so that the test
can restart daemons the same way on vstart as in full blown teuthology.
For branch wip-manila
Signed-off-by: John Spray <john.spray@redhat.com>
This class is meant to quack like a DaemonState,
so it needs to expose a .proc attribute. This
was breaking TestDamageTable.
Signed-off-by: John Spray <john.spray@redhat.com>
The "ps au" output was truncating lines which could cause
processes to get missed in some cases, like where there
is a long --client-mountpoint argument.
Signed-off-by: John Spray <john.spray@redhat.com>
Mostly checking the output from the status asok is awkward
because you need to get the system stuck in a particular
state to do so. However, we already have a test here
that sticks the system in reconnect, so here's some
very light test coverage for that asok.
Signed-off-by: John Spray <john.spray@redhat.com>
test_ops_throttle was catching misbehaviour when
deleting lots of files in a directory, but
we should have a non-throttle test for that case
so that it's clearer what's gone wrong.
Signed-off-by: John Spray <john.spray@redhat.com>
...because new tests that modify the client ID will
get confused about whether they're mounted or not, otherwise.
Signed-off-by: John Spray <john.spray@redhat.com>
