Because these tests exercise subtle interactions
in the Client->ObjectCacher->Objecter stack,
enable the verbose logging for the lower layers
too.
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>
Previously teuthology read test path from ctx.teuthology_config,
now it reads it from the global teuthology.config.config object.
This was breaking test_journal_migration because it uses tasks/workunit,
when run with vstart_runner.
Signed-off-by: John Spray <john.spray@redhat.com>
This was getting stressed in new ways by
TestSessionMap.test_session_reject, which
has a mount that fails initially.
Two changes here:
* Raise CommandFailedError instead of RuntimeError when
a mount fails (i.e. catch process termination instead
of timing out on /sys/ population)
* Generalise error handling on umount, so that we only
raise the exception on an umount failure if the mount
appears to really not be unmounted. There is some
EINVAL corner case that was getting triggered by the test.
Signed-off-by: John Spray <john.spray@redhat.com>
Analogous to raw_cluster_command, but instead
of calling blocking CLI command we're invoking
the -w mode.
Signed-off-by: John Spray <john.spray@redhat.com>
Used when configuring clients with dynamically
generated auth keys, and pointing them at mount paths.
Signed-off-by: John Spray <john.spray@redhat.com>
When stray directory inodes are corrupted, MDS may go to damaged state
after becoming active. (MDCache::open_root/populate_mydir is called by
MDSRank::starting_done).
Fixes: #14196
Signed-off-by: Yan, Zheng <zyan@redhat.com>
We were waiting for teh dameon to fail, not for the mons to notice,
which meant that after we restart the daemon the next tell could
try to talk to the old osd.
Signed-off-by: Sage Weil <sage@redhat.com>
This checks locking problems. This can be a separate facet for
workunits, but for now it requires a manual 2nd configuration for
rbd_fsx.
Signed-off-by: Josh Durgin <jdurgin@redhat.com>