The `subset` option is important in Teuthology runs for reducing the number of tests that are triggered. This option is outlined in another part of the Teuthology documentation, but I think it's important to place here as well.
Also, -n (for how many times the job will run) is incorrect; it should be -N.
Signed-off-by: Laura Flores <lflores@redhat.com>
* refs/pull/43590/head:
qa: test that new mounts of same fs function after old mount is evicted
qa: remove REQUIRE_KCLIENT_REMOTE
Reviewed-by: Patrick Donnelly <pdonnell@redhat.com>
Reviewed-by: Xiubo Li <xiubli@redhat.com>
* refs/pull/43595/head:
client: do not defer releasing caps when revoking
Reviewed-by: Jeff Layton <jlayton@redhat.com>
Reviewed-by: Patrick Donnelly <pdonnell@redhat.com>
rgw: fix debug build of OpsLogFile
Reviewed-by: Cory Snyder <csnyder@iland.com>
Reviewed-by: Willem Jan Withagen <wjw@digiware.nl>
Reviewed-by: Matt Benjamin <mbenjamin@redhat.com>
mgr/cephadm: track daemon deployment post actions by daemon name instead of type
Reviewed-by: Michael Fritch <mfritch@suse.com>
Reviewed-by: Sebastian Wagner <sewagner@redhat.com>
cephadm: fix tracebacks that could occur during apply spec
Reviewed-by: Adam King <adking@redhat.com>
Reviewed-by: Dimitri Savineau <dsavinea@redhat.com>
Reviewed-by: Sebastian Wagner <sewagner@redhat.com>
Consider the following workload:
writeA(0, 4096)
writeB(0, 512).
pwl can makre sure writeA persist to cache before writeB.
But when flush to osd, it use async-read to read data from cache and in
the callback function they issue write to osd.
So although we by order issue aio-read(4096), aio-read(512). But we
can't make sure the return order.
If aio-read(512) firstly return, the write order to next layer is
writeB(0, 512)
writeA(0, 4096).
This is wrong from the user point.
To avoid this occur, we should firstly read all data from cache. And
then send write by order.
Fiexs: https://tracker.ceph.com/issues/52511
Tested-by: Feng Hualong <hualong.feng@intel.com>
Signed-off-by: Jianpeng Ma <jianpeng.ma@intel.com>
can't use ceph::mutex locks with std::condition_variable::wait() in
debug builds. use the ceph::condition_variable wrapper instead
Signed-off-by: Casey Bodley <cbodley@redhat.com>
mgr/dashboard: all pyfakefs must be pinned on same version
Reviewed-by: Ernesto Puerta <epuertat@redhat.com>
Reviewed-by: ljflores <NOT@FOUND>
Reviewed-by: Nizamudeen A <nia@redhat.com>
Reviewed-by: rishabh-d-dave <NOT@FOUND>
Without this patch execution of install-deps.sh fails with an error.
Fixes: https://tracker.ceph.com/issues/53088
Signed-off-by: Rishabh Dave <ridave@redhat.com>
This reverts commit 78d6ac0d35, reversing
changes made to 9a8de97f7a.
This broke cephadm (infers config when it should not)
Signed-off-by: Sage Weil <sage@newdream.net>
doc/releases/pacific.rst: add note about data corruption bug
Reviewed-by: Igor Fedotov <igor.fedotov@croit.io>
Reviewed-by: Laura Flores <lflores@redhat.com>
msg/async: support disabling data crc for protocol v2
Reviewed-by: Radoslaw Zarzynski <rzarzyns@redhat.com>
Reviewed-by: Chunmei Liu <chunmei.liu@intel.com>
Reviewed-by: Yingxin Cheng <yingxin.cheng@intel.com>
To fix failure like
Failure Reason:
Command failed on smithi085 with status 1: 'sudo yum -y install ceph-volume'
Signed-off-by: Neha Ojha <nojha@redhat.com>
