ceph/qa
Vikhyat Umrao 90144aa64c auth: 'ceph auth import -i' overwrites caps, if caps are not specified
in given keyring file, should alert user and should not allow this import.
Because in 'ceph auth list' we keep all the keyrings with caps and importing
'client.admin' user keyring without caps locks the cluster with error[1]
because admin keyring caps are missing in 'ceph auth'.

[1] Error connecting to cluster: PermissionDeniedError

Fixes: http://tracker.ceph.com/issues/18932

Signed-off-by: Vikhyat Umrao <vumrao@redhat.com>
2017-02-20 03:48:31 +05:30
..
archs
btrfs
ceph-deploy-overrides
cephfs
client
clusters
config qa/config/rados.yaml: enable osd_debug_verify_cached_snaps 2016-12-15 10:50:49 -08:00
config_options
debug
distros tests: update SUSE yaml facets in qa/distros/all 2017-02-08 15:27:00 +01:00
erasure-code
fs
libceph
machine_types changed script name 2016-12-20 15:34:56 -08:00
mds
mon/bootstrap
mon_kv_backend
nightlies
objectstore
overrides tests: override yaml to set client pid file to empty string 2017-01-06 12:05:31 +01:00
packages
qa_scripts tests: drop rbd_cli_tests.pl and RbdLib.pm 2017-01-08 16:17:08 +01:00
rbd
releases qa/rados/upgrade/jewel-x-singleton: run luminous.yaml at the end 2017-02-12 09:47:41 -05:00
rgw_pool_type
suites qa: add workunit to test krbd data-pool support 2017-02-16 22:42:46 +01:00
tasks Revert "qa/tasks/workunit: use the suite repo for cloning workunit" 2017-02-17 11:54:27 -06:00
timezone
workunits auth: 'ceph auth import -i' overwrites caps, if caps are not specified 2017-02-20 03:48:31 +05:30
.gitignore
loopall.sh
Makefile
README
run_xfstests_krbd.sh
run_xfstests_qemu.sh
run_xfstests-obsolete.sh
run_xfstests.sh
runallonce.sh
runoncfuse.sh
runonkclient.sh
setup-chroot.sh
tox.ini

ceph-qa-suite
-------------

clusters/    - some predefined cluster layouts
suites/      - set suite

The suites directory has a hierarchical collection of tests.  This can be
freeform, but generally follows the convention of

  suites/<test suite name>/<test group>/...

A test is described by a yaml fragment.

A test can exist as a single .yaml file in the directory tree.  For example:

 suites/foo/one.yaml
 suites/foo/two.yaml

is a simple group of two tests.

A directory with a magic '+' file represents a test that combines all
other items in the directory into a single yaml fragment.  For example:

 suites/foo/bar/+
 suites/foo/bar/a.yaml
 suites/foo/bar/b.yaml
 suites/foo/bar/c.yaml

is a single test consisting of a + b + c.

A directory with a magic '%' file represents a test matrix formed from
all other items in the directory.  For example,

 suites/baz/%
 suites/baz/a.yaml
 suites/baz/b/b1.yaml
 suites/baz/b/b2.yaml
 suites/baz/c.yaml
 suites/baz/d/d1.yaml
 suites/baz/d/d2.yaml

is a 4-dimensional test matrix.  Two dimensions (a, c) are trivial (1
item), so this is really 2x2 = 4 tests, which are

  a + b1 + c + d1
  a + b1 + c + d2
  a + b2 + c + d1
  a + b2 + c + d2

Symlinks are okay.

The teuthology code can be found in https://github.com/ceph/teuthology.git