vm-stop doesn't fully support -p sec
Bug #1008852 reported by
Micah Gersten
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Tools used by the Ubuntu QA Team |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
When I run vm-stop -u -p sec, if the VM doesn't respond after 60 or 90 seconds, then the script will try to ssh to sec which doesn't exist.
vm-stop -u -p sec
'sec-lucid-amd64' is not running
'sec-natty-amd64' is not running
'sec-oneiric-amd64' is not running
Domain sec-precise-amd64 is being shutdown
INFO: waiting for 'sec-precise-amd64' to shutdown
WARN: 'sec-precise-amd64' did not stop after '90' seconds. Using:
WARN: $ ssh -p sec -l root "" "shutdown"
ssh: Could not resolve hostname : Name or service not known
Revision history for this message
| Steve Beattie (sbeattie) wrote | #1 |
| Changed in ubuntu-qa-tools: | |
| status: | New → Fix Released |
To post a comment you must log in.
vm-stop has been deprecated, uvt is now the preferred tool. I believe it handles this case properly. Thanks!