it gets stuck when connecting to its auth_uri
Bug #1645144 reported by
tarik
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tempest |
Expired
|
Undecided
|
Unassigned |
Bug Description
Hi,
When i trying to run tempest on our Mitaka environment, I am getting following errors and none of the test start.
ArgsAlreadyPars
When i try to run that command for checking i get timeout.
python -m testtools.run tempest.
I attach tempest output also.
Thank You,
Tarik.
To post a comment you must log in.
You should use test_discover to discover tests i.e. -t ./tempest/ test_discover.
Even better, to run tests you can use tox directly:
tox -eall -- [regex]
Or the "tempest run" command.
(tempest) andreafrittoli@ galadriel: /git/openstack. org/openstack/ tempest$ tempest run --help
[- -workspace- path WORKSPACE_PATH]
[- -config- file CONFIG_FILE] [--smoke | --regex REGEX]
[- -whitelist- file WHITELIST_FILE | --blacklist-file BLACKLIST_FILE]
[- -list-tests] [--concurrency CONCURRENCY]
[- -parallel | --serial] [--subunit]
usage: tempest run [-h] [--workspace WORKSPACE]
Run tempest
optional arguments:
Name of tempest workspace to use for running tests.
You can see a list of workspaces with tempest
workspace list
The path to the workspace file, the default is
~/.tempest/ workspace. yaml
Configuratio n file to run tempest with
A normal testr selection regex used to specify a
subset of tests to run
Path to a whitelist file, this file contains a
separate regex on each newline.
Path to a blacklist file, this file contains a
separate regex exclude on each newline
The number of workers to use, defaults to the number
of cpus
-h, --help show this help message and exit
--workspace WORKSPACE
--workspace-path WORKSPACE_PATH
--config-file CONFIG_FILE
--smoke Run the smoke tests only
--regex REGEX, -r REGEX
--whitelist-file WHITELIST_FILE, --whitelist_file WHITELIST_FILE
--blacklist-file BLACKLIST_FILE, --blacklist_file BLACKLIST_FILE
--list-tests, -l List tests
--concurrency CONCURRENCY, -w CONCURRENCY
--parallel Run tests in parallel (this is the default)
--serial Run tests serially
--subunit Enable subunit v2 output