Github user swill commented on the issue:
https://github.com/apache/cloudstack/pull/872
@rhtyd have you gotten this system VM to build? I am having trouble
getting it to finish building.
My build is failing here...
```
+ log DEBUG 'on_exit: clean_vbox'
+ local level=DEBUG
+ shift
+ [[ 1 != \1 ]]
+ local code=
++ date '+%F %T'
+ local 'line=[2016-09-19 17:55:41] DEBUG: on_exit: clean_vbox'
+ '[' -t 2 ']'
+ echo '[2016-09-19 17:55:41] DEBUG: on_exit: clean_vbox'
[2016-09-19 17:55:41] DEBUG: on_exit: clean_vbox
+ eval clean_vbox
++ clean_vbox
++ log INFO 'deleting all virtualbox vms and disks for jenkins'
++ local level=INFO
++ shift
++ [[ 1 != \1 ]]
++ local code=
+++ date '+%F %T'
++ local 'line=[2016-09-19 17:55:41] INFO: deleting all virtualbox vms and
disks for jenkins'
++ '[' -t 2 ']'
++ echo '[2016-09-19 17:55:41] INFO: deleting all virtualbox vms and disks
for jenkins'
[2016-09-19 17:55:41] INFO: deleting all virtualbox vms and disks for
jenkins
++ bundle exec ./vbox_vm_clean.rb --delete --kill
++ bundle exec ./vbox_disk_clean.rb
+ (( i-- ))
+ (( i>=0 ))
... it just hangs here for hours ...
```
To make sure it is not my jenkins box which has a problem, I try building
my port of the changes (https://github.com/swill/cloudstack/tree/strongswan)
made in this PR (prior to the latest update, back when it still had merge
conflicts), and that builds fine.
Jenkins is basically running:
```
whoami
export PATH=/home/jenkins/.rvm/bin:$PATH
export rvm_path=/home/jenkins/.rvm
export HOME=/home/jenkins/
#wget
http://download.virtualbox.org/virtualbox/4.2.6/VBoxGuestAdditions_4.2.6.iso
cd tools/appliance
if [ -d iso ]; then
rm -fvr iso
fi
if [ -d dist ]; then
rm -fvr dist
fi
if [ -d box ]; then
rm -fvr box
fi
if [ -d /home/jenkins/iso ]; then
cp -rv /home/jenkins/iso .
fi
if [ ! -d iso ]; then
mkdir iso
ln -s $WORKSPACE/*.iso iso/
fi
export clean_vbox=1
export BUILD_NUMBER=
export version=4.6.0
export branch=master
chmod +x build.sh
./build.sh systemvm64template
```
Any ideas???
---
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.
---
