Don't need to explicitly turn off the test during some upgrades
Leaving disabled until merge of import/export fixes
Fixes: #9805
Signed-off-by: David Zafman <dzafman@redhat.com>
Add the distros directory which enumerates the os_type and
os_version on which the suite is to run.
http://tracker.ceph.com/issues/9660Fixes: #9660
Signed-off-by: Loic Dachary <loic-201408@dachary.org>
(cherry picked from commit 16e564ec8d)
We want to avoid tests that time out due to a too slow backend.
Reviwed-by: Josh Durgin <josh.durgin@inktank.com>
Signed-off-by: Yehuda Sadeh <yehuda@redhat.com>
(cherry picked from commit 85221bc325)
Mimic upgrade/firefly-x/stress-split only with thrashosd configured with
min_in: 4 for k=3,m=1 . All erasure code workloads are moved in this
dedicated suite.
http://tracker.ceph.com/issues/9652Fixes: #9652
Signed-off-by: Loic Dachary <loic-201408@dachary.org>
Conflicts:
suites/upgrade/firefly-x/stress-split-erasure-code/3-thrash/default.yaml
Because thrashosd does not have min_in: 4 and that we don't want to set
it because other workloads may be influenced.
Signed-off-by: Loic Dachary <loic-201408@dachary.org>
Because it needs the thrasher to have min_in: 4 otherewise k=3,m=1 will
block.
http://tracker.ceph.com/issues/9648Fixes: #9648
Signed-off-by: Loic Dachary <loic-201408@dachary.org>
Other rados put will fail as follows
$ touch /tmp/bar
$ ./rados -p rbd put existing_3 /tmp/bar
$ ./rados -p rbd put existing_3 /tmp/bar
WARNING: could not create object: existing_3
error putting rbd/existing_3: (17) File exists
it should be considered a bug in the rados command line but needs to be
addressed separately.
http://tracker.ceph.com/issues/9387Fixes: #9387
Signed-off-by: Loic Dachary loic-201408@dachary.org
The ec-rados-default.yaml was linked to suites as if it was a task
although it is a workload intended for parallel upgrade tests.
The ec-rados-plugin=jerasure-k=2-m=1.yaml task is defined and used
instead, where relevant.
http://tracker.ceph.com/issues/9549Fixes: #9549
Signed-off-by: Loic Dachary <loic-201408@dachary.org>
Conflicts:
suites/upgrade/dumpling-firefly-giant/parallel/6-giant-workload/ec-rados-plugin=jerasure-k=3-m=1.yaml
suites/upgrade/dumpling-firefly-x/parallel/7-final-workload/ec-rados-plugin=jerasure-k=3-m=1.yaml
suites/upgrade/firefly-x/stress-split-erasure-code/5-workload/ec-rados-default.yaml
Adding this so that we can modify the clients' conf file as needed with slow backend.
This can be achieved by:
overrides:
s3tests:
slow_backend: true
Signed-off-by: Yehuda Sadeh <yehuda@redhat.com>
(cherry picked from commit 61409179df)
Dumpling does not properly order reads (w/ RWORDERED) vs writes. The code
controlling that was totally rewritten in firefly. It's not worth backporting.
Signed-off-by: Sage Weil <sage@redhat.com>
