Adding simple checks examination of data/logs after robot suites 89/50989/5
authorJamo Luhrsen <jluhrsen@redhat.com>
Wed, 25 Jan 2017 03:50:19 +0000 (19:50 -0800)
committerJamo Luhrsen <jluhrsen@redhat.com>
Fri, 10 Feb 2017 00:01:30 +0000 (16:01 -0800)
this was found useful in the case when karaf logs were not able to be archived
because of a controller bug which caused them to be so bloated that jenkins
would choke and exit. This patch would at least give some clue in the console
log in that case.

Change-Id: Iacf4e2475f6525e781549e7a9eefb18a2041cc88
Signed-off-by: Jamo Luhrsen <jluhrsen@redhat.com>
jjb/integration/include-raw-integration-deploy-controller-run-test.sh
jjb/integration/include-raw-integration-deploy-openstack-run-test.sh
jjb/integration/include-raw-integration-start-cluster-run-test.sh

index 0fe7c0ab1da0d353365c5d7989971a93643f79ac..ced677afbb988d11888999093a8512a768e1d498 100644 (file)
@@ -273,6 +273,10 @@ pybot -N ${TESTPLAN} --removekeywords wuks -c critical -e exclude -v BUNDLEFOLDE
 -v MININET_USER:${USER} -v USER_HOME:${HOME} ${TESTOPTIONS} ${SUITES} || true
 # FIXME: Sort (at least -v) options alphabetically.
 
+echo "Examining the files in data/log and checking filesize"
+ssh ${ODL_SYSTEM_IP} "ls -altr /tmp/${BUNDLEFOLDER}/data/log/"
+ssh ${ODL_SYSTEM_IP} "du -hs /tmp/${BUNDLEFOLDER}/data/log/*"
+
 for i in `seq 1 ${NUM_ODL_SYSTEM}`
 do
     CONTROLLERIP=ODL_SYSTEM_${i}_IP
index ec27df15ab09bafb063cc1594faeb9e7471b942c..182274338450fa12204f7fcefdf08467269639be 100644 (file)
@@ -646,6 +646,10 @@ pybot -N ${TESTPLAN} --removekeywords wuks -c critical -e exclude \
     -v WORKSPACE:/tmp \
     ${TESTOPTIONS} ${SUITES} || true
 
+echo "Examining the files in data/log and checking filesize"
+ssh ${ODL_SYSTEM_IP} "ls -altr /tmp/${BUNDLEFOLDER}/data/log/"
+ssh ${ODL_SYSTEM_IP} "du -hs /tmp/${BUNDLEFOLDER}/data/log/*"
+
 echo "Tests Executed"
 DEVSTACK_TEMPEST_DIR="/opt/stack/tempest"
 if $(ssh ${OPENSTACK_CONTROL_NODE_IP} "sudo sh -c '[ -f ${DEVSTACK_TEMPEST_DIR}/.testrepository/0 ]'"); then # if Tempest results exist
index 2907832f7d296e5eb127042e98f2cfc7d0a08fe3..ab79025604a601de3b80fc9657a4cb7f4dc0cba4 100644 (file)
@@ -120,6 +120,14 @@ TOOLS_SYSTEM_IP:${TOOLS_SYSTEM_IP} ${tools_variables} -v NUM_TOOLS_SYSTEM:${NUM_
 -v USER_HOME:${HOME} ${TESTOPTIONS} ${SUITES} || true
 # FIXME: Sort (at least -v) options alphabetically.
 
+echo "Examining the files in data/log and checking filesize"
+ssh ${ODL_SYSTEM_1_IP} "ls -altr /tmp/${BUNDLEFOLDER}/data/log/"
+ssh ${ODL_SYSTEM_1_IP} "du -hs /tmp/${BUNDLEFOLDER}/data/log/*"
+ssh ${ODL_SYSTEM_2_IP} "ls -altr /tmp/${BUNDLEFOLDER}/data/log/"
+ssh ${ODL_SYSTEM_2_IP} "du -hs /tmp/${BUNDLEFOLDER}/data/log/*"
+ssh ${ODL_SYSTEM_3_IP} "ls -altr /tmp/${BUNDLEFOLDER}/data/log/"
+ssh ${ODL_SYSTEM_3_IP} "du -hs /tmp/${BUNDLEFOLDER}/data/log/*"
+
 set +e  # We do not want to create red dot just because something went wrong while fetching logs.
 for i in `seq 1 ${NUM_ODL_SYSTEM}`
 do