Bug #7930
closedteuthology-nuke with no args gives traceback instead of usage
0%
Description
virtualenv)vagrant@ubuntu:~/teuthology$ teuthology-nuke
Traceback (most recent call last):
File "/home/vagrant/teuthology/virtualenv/bin/teuthology-nuke", line 9, in <module>
load_entry_point('teuthology==0.0.1', 'console_scripts', 'teuthology-nuke')()
File "/home/vagrant/teuthology/scripts/nuke.py", line 10, in main
teuthology.nuke.main(parse_args())
File "/home/vagrant/teuthology/teuthology/nuke.py", line 305, in main
ctx.config['targets'],
KeyError: 'targets'
(virtualenv)vagrant@ubuntu:~/teuthology$ teuthology-nuke --help
usage: teuthology-nuke [-h] [-v] [-t CONFIG [CONFIG ...]] [-a DIR]
[--owner OWNER] [-p PID] [-r] [-s] [-u] [-n NAME] [-i]
Reset test machines
optional arguments:
-h, --help show this help message and exit
-v, --verbose be more verbose
-t CONFIG [CONFIG ...], --targets CONFIG [CONFIG ...]
yaml config containing machines to nuke
-a DIR, --archive DIR
archive path for a job to kill and nuke
--owner OWNER job owner
-p PID, --pid PID pid of the process to be killed
-r, --reboot-all reboot all machines
-s, --synch-clocks synchronize clocks on all machines
-u, --unlock Unlock each successfully nuked machine, and output targets thatcould not be nuked.
-n NAME, --name NAME Name of run to cleanup
-i, --noipmi Skip ipmi checking
Examples:
teuthology-nuke -t target.yaml --unlock --owner user@host
teuthology-nuke -t target.yaml --pid 1234 --unlock --owner user@host
Updated by Zack Cerza over 9 years ago
- Status changed from New to Resolved
- Assignee set to Zack Cerza