Github user lsimons commented on the pull request:
https://github.com/apache/cloudstack/pull/16#issuecomment-56387394
sorry, nevermind the last comment.
From the jenkins build log:
```
[2014-09-19 14:57:59] INFO: stoppping all virtualbox vms for jenkins
+ bundle exec ./vbox_vm_clean.rb
VBoxManage controlvm systemvmtemplate poweroff
VBoxManage: error: Invalid machine state: PoweredOff (must be Running,
Paused or Stuck)
VBoxManage: error: Details: code VBOX_E_INVALID_VM_STATE (0x80bb0002),
component Console, interface IConsole, callee nsISupports
VBoxManage: error: Context: "PowerDown(progress.asOutParam())" at line 222
of file VBoxManageControlVM.cpp
VBoxManage controlvm systemvm64template poweroff
VBoxManage: error: Invalid machine state: PoweredOff (must be Running,
Paused or Stuck)
VBoxManage: error: Details: code VBOX_E_INVALID_VM_STATE (0x80bb0002),
component Console, interface IConsole, callee nsISupports
VBoxManage: error: Context: "PowerDown(progress.asOutParam())" at line 222
of file VBoxManageControlVM.cpp
kill -SIGKILL 19324
kill -SIGTERM 19324
./vbox_vm_clean.rb:49:in `kill'
./vbox_vm_clean.rb:49:in `block (2 levels) in <main>'
/usr/local/rvm/gems/ruby-1.9.3-p547/gems/sys-proctable-0.9.4-universal-linux/lib/linux/sys/proctable.rb:237:in
`block in ps'
/usr/local/rvm/gems/ruby-1.9.3-p547/gems/sys-proctable-0.9.4-universal-linux/lib/linux/sys/proctable.rb:110:in
`foreach'
/usr/local/rvm/gems/ruby-1.9.3-p547/gems/sys-proctable-0.9.4-universal-linux/lib/linux/sys/proctable.rb:110:in
`ps'
./vbox_vm_clean.rb:31:in `block in <main>'
./vbox_vm_clean.rb:14:in `each'
./vbox_vm_clean.rb:14:in `<main>'
VBoxManage controlvm systemvm64template-systemvm-refactor-for-upstream-9
poweroff
VBoxManage: error: Invalid machine state: Aborted (must be Running, Paused
or Stuck)
VBoxManage: error: Details: code VBOX_E_INVALID_VM_STATE (0x80bb0002),
component Console, interface IConsole, callee nsISupports
VBoxManage: error: Context: "PowerDown(progress.asOutParam())" at line 222
of file VBoxManageControlVM.cpp
```
The lines
```bash
kill -SIGKILL 19324
kill -SIGTERM 19324
```
mean that we forcibly shut down a virtualbox process, probably the one that
was running the systemvm that was built. This means that the line further up
```bash
bundle exec veewee vbox halt
systemvm64template-systemvm-refactor-for-upstream-9
```
did not succeed in fully shutting down the new machine, and then the next
attempt to cleanly power off
```bash
VBoxManage controlvm systemvm64template-systemvm-refactor-for-upstream-9
poweroff
```
also failed, and so we don't umount cleanly, and so stuff is broken.
FWIW, a successful build has something more like
```bash
VBoxManage controlvm systemvmtemplate-systemvm-persistent-config-4.5.0.78
poweroff
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%```
```
I'll investigate what went wrong.
We should probably also just fail the build if the poweroff fails rather
than attempting a 'kill'.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
