See <http://jenkins.buildacloud.org/job/simulator-singlerun/1104/changes>
Changes: [sanjay.tripathi] CLOUDSTACK-8386: CS is returning sec. storage even if it is full and there are other sec. storage with free space. ------------------------------------------ [...truncated 10447 lines...] ========> Processing SQL file at <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/target/db/cloudbridge_schema.sql> ========> Processing SQL file at <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/target/db/cloudbridge_multipart.sql> ========> Processing SQL file at <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/target/db/cloudbridge_index.sql> ========> Processing SQL file at <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/target/db/cloudbridge_multipart_alter.sql> ========> Processing SQL file at <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/target/db/cloudbridge_bucketpolicy.sql> ========> Processing SQL file at <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/target/db/cloudbridge_policy_alter.sql> ========> Processing SQL file at <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/target/db/cloudbridge_offering.sql> ========> Processing SQL file at <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/target/db/cloudbridge_offering_alter.sql> ========> Processing SQL file at <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/developer-prefill.sql> ========> Processing upgrade: com.cloud.upgrade.DatabaseUpgradeChecker [INFO] [INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ cloud-developer --- [INFO] [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ cloud-developer --- [INFO] Installing <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/pom.xml> to /var/lib/jenkins/.m2/repository/org/apache/cloudstack/cloud-developer/4.6.0-SNAPSHOT/cloud-developer-4.6.0-SNAPSHOT.pom [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 2:04.229s [INFO] Finished at: Tue Apr 14 07:13:22 EDT 2015 [INFO] Final Memory: 44M/198M [INFO] ------------------------------------------------------------------------ [WARNING] The requested profile "simulator" could not be activated because it does not exist. [simulator-singlerun] $ mvn -P developer -pl developer -Ddeploydb-simulator [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Apache CloudStack Developer Mode 4.6.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ cloud-developer --- [INFO] Starting audit... Audit done. [INFO] [INFO] --- properties-maven-plugin:1.0-alpha-2:read-project-properties (default) @ cloud-developer --- [WARNING] Ignoring missing properties file: <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/../utils/conf/db.properties.override> [INFO] [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-developer --- [INFO] [INFO] --- maven-antrun-plugin:1.8:run (default) @ cloud-developer --- [INFO] Executing tasks main: [INFO] Executed tasks [INFO] [INFO] >>> exec-maven-plugin:1.2.1:java (create-schema-simulator) @ cloud-developer >>> [INFO] [INFO] --- maven-checkstyle-plugin:2.11:check (cloudstack-checkstyle) @ cloud-developer --- [INFO] Starting audit... Audit done. [INFO] [INFO] <<< exec-maven-plugin:1.2.1:java (create-schema-simulator) @ cloud-developer <<< [INFO] [INFO] --- exec-maven-plugin:1.2.1:java (create-schema-simulator) @ cloud-developer --- log4j:WARN No appenders could be found for logger (org.springframework.core.env.StandardEnvironment). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. ========> WARNING: Provided file does not exist: <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/../utils/conf/db.properties.override> ========> Initializing database=simulator with host=localhost port=3306 username=cloud password=cloud ============> Running query: drop database if exists `simulator` ============> Running query: create database `simulator` ============> Running query: GRANT ALL ON simulator.* to 'cloud'@`localhost` identified by 'cloud' ============> Running query: GRANT ALL ON simulator.* to 'cloud'@`%` identified by 'cloud' ========> Processing SQL file at <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/target/db/create-schema-simulator.sql> ========> Processing SQL file at <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/target/db/templates.simulator.sql> ========> Processing SQL file at <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/target/db/hypervisor_capabilities.simulator.sql> ========> Processing upgrade: com.cloud.upgrade.DatabaseUpgradeChecker [INFO] [INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ cloud-developer --- [INFO] [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ cloud-developer --- [INFO] Installing <http://jenkins.buildacloud.org/job/simulator-singlerun/ws/developer/pom.xml> to /var/lib/jenkins/.m2/repository/org/apache/cloudstack/cloud-developer/4.6.0-SNAPSHOT/cloud-developer-4.6.0-SNAPSHOT.pom [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 25.827s [INFO] Finished at: Tue Apr 14 07:13:50 EDT 2015 [INFO] Final Memory: 44M/160M [INFO] ------------------------------------------------------------------------ [simulator-singlerun] $ /bin/bash -x /tmp/hudson6956837738685876555.sh + grep -q Launcher + jps -l + rm -f xunit.xml + echo '' + rm -rf /tmp/MarvinLogs + echo Check for initialization of the management server Check for initialization of the management server + COUNTER=0 + SERVER_PID=28157 + mvn -P systemvm,simulator -pl :cloud-client-ui jetty:run + '[' 0 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=1 + '[' 1 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=2 + '[' 2 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=3 + '[' 3 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=4 + '[' 4 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=5 + '[' 5 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=6 + '[' 6 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=7 + '[' 7 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=8 + '[' 8 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=9 + '[' 9 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=10 + '[' 10 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=11 + '[' 11 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=12 + '[' 12 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=13 + '[' 13 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=14 + '[' 14 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=15 + '[' 15 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=16 + '[' 16 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=17 + '[' 17 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=18 + '[' 18 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=19 + '[' 19 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=20 + '[' 20 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=21 + '[' 21 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=22 + '[' 22 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=23 + '[' 23 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=24 + '[' 24 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + sleep 5 + COUNTER=25 + '[' 25 -lt 44 ']' + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + break + grep -q 'Management server node 127.0.0.1 is up' jetty-output.out + echo Started OK pid 28157 Started OK pid 28157 + sleep 20 + export PYTHONPATH=<http://jenkins.buildacloud.org/job/simulator-singlerun/ws/tools/marvin> + PYTHONPATH=<http://jenkins.buildacloud.org/job/simulator-singlerun/ws/tools/marvin> + python2.6 tools/marvin/marvin/deployDataCenter.py -i setup/dev/advanced.cfg /usr/lib/python2.6/site-packages/pycrypto-2.6-py2.6-linux-x86_64.egg/Crypto/Util/number.py:57: PowmInsecureWarning: Not using mpz_powm_sec. You should rebuild using libgmp >= 5 to avoid timing attack vulnerability. _warn("Not using mpz_powm_sec. You should rebuild using libgmp >= 5 to avoid timing attack vulnerability.", PowmInsecureWarning) ==== Log Folder Path: /tmp//MarvinLogs//DeployDataCenter__Apr_14_2015_07_16_19_OWNX8D. All logs will be available here ==== ==== Deploy DC Started ==== === Data Center Settings are dumped to /tmp//MarvinLogs//DeployDataCenter__Apr_14_2015_07_16_19_OWNX8D/dc_entries.obj=== ====Deploy DC Successful===== + sleep 60 + /usr/local/bin/nosetests-2.7 -v --with-marvin --marvin-config=setup/dev/advanced.cfg --with-xunit --xunit-file=xunit.xml -a tags=advanced,required_hardware=false --zone=Sandbox-simulator --hypervisor=simulator -w test/integration/smoke /usr/local/lib/python2.7/site-packages/nose-1.3.3-py2.7.egg/nose/plugins/manager.py:395: RuntimeWarning: Unable to load plugin marvinPlugin = marvin.marvinPlugin:MarvinPlugin: netaddr>=0.7.14 RuntimeWarning) Usage: nosetests-2.7 [options] nosetests-2.7: error: no such option: --with-marvin + mvn -P systemvm,simulator -pl :cloud-client-ui jetty:stop [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Apache CloudStack Client UI 4.6.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-jetty-plugin:6.1.26:stop (default-cli) @ cloud-client-ui --- [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 3.640s [INFO] Finished at: Tue Apr 14 07:20:14 EDT 2015 [INFO] Final Memory: 26M/116M [INFO] ------------------------------------------------------------------------ + sleep 10 + kill -KILL 28157 /tmp/hudson6956837738685876555.sh: line 44: kill: (28157) - No such process + rm -rf '*.log.*' [locks-and-latches] Releasing all the locks [locks-and-latches] All the locks released [xUnit] [INFO] - Starting to record. [xUnit] [INFO] - Processing JUnit [xUnit] [INFO] - [JUnit] - 1 test report file(s) were found with the pattern 'xunit.xml' relative to '<http://jenkins.buildacloud.org/job/simulator-singlerun/ws/'> for the testing framework 'JUnit'. [xUnit] [ERROR] - The result file '<http://jenkins.buildacloud.org/job/simulator-singlerun/ws/xunit.xml'> for the metric 'JUnit' is not valid. The result file has been skipped. [xUnit] [INFO] - Failing BUILD because 'set build failed if errors' option is activated. [xUnit] [INFO] - There are errors when processing test results. [xUnit] [INFO] - Skipping tests recording. [xUnit] [INFO] - Stop build. Build step 'Publish xUnit test result report' changed build result to FAILURE