Harikrishna Patnala created CLOUDSTACK-6375: -----------------------------------------------
Summary: 4.3 system vm template job failing in jenkins Key: CLOUDSTACK-6375 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6375 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: SystemVM Affects Versions: 4.3.0 Reporter: Harikrishna Patnala Assignee: Abhinandan Prateek Fix For: 4.3.0 4.3 system vm template job failing; looks like build falling after the getting updated openssl 1.0.1e-2+deb7u6. http://jenkins.buildacloud.org/view/4.3/job/cloudstack-4.3-systemvm64/140/console (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 24061 files and directories currently installed.) Preparing to replace libssl1.0.0:amd64 1.0.1e-2 (using .../libssl1.0.0_1.0.1e-2+deb7u6_amd64.deb) ... Unpacking replacement libssl1.0.0:amd64 ... Selecting previously unselected package libc-dev-bin. Unpacking libc-dev-bin (from .../libc-dev-bin_2.13-38+deb7u1_amd64.deb) ... Selecting previously unselected package linux-libc-dev:amd64. Unpacking linux-libc-dev:amd64 (from .../linux-libc-dev_3.2.54-2_amd64.deb) ... Selecting previously unselected package libc6-dev:amd64. Unpacking libc6-dev:amd64 (from .../libc6-dev_2.13-38+deb7u1_amd64.deb) ... Selecting previously unselected package uuid-dev. Unpacking uuid-dev (from .../uuid-dev_2.20.1-5.3_amd64.deb) ... Selecting previously unselected package libapr1-dev. Unpacking libapr1-dev (from .../libapr1-dev_1.4.6-3+deb7u1_amd64.deb) ... Selecting previously unselected package zlib1g-dev:amd64. Unpacking zlib1g-dev:amd64 (from .../zlib1g-dev_1%3a1.2.7.dfsg-13_amd64.deb) ... Selecting previously unselected package libssl-dev. Unpacking libssl-dev (from .../libssl-dev_1.0.1e-2+deb7u6_amd64.deb) ... Selecting previously unselected package libtcnative-1. Unpacking libtcnative-1 (from .../libtcnative-1_1.1.24-1_amd64.deb) ... Processing triggers for man-db ... Setting up libssl1.0.0:amd64 (1.0.1e-2+deb7u6) ... Checking for services that may need to be restarted...done. Checking init scripts... [?1049h[1;24r[4l[?25l(B[m[37m[40m[1;24r[H[2J[1;1H[1m[37m[44m [2;1H [3;1H [4;1H [5;1H [6;1H [7;1H [8;1H [9;1H [10;1H [11;1H [12;1H [13;1H [14;1H [15;1H [16;1H [17;1H [18;1H [19;1H [20;1H [21;1H [22;1H [23;1H [24;1H [24;79H [4h [4l[1;1H(B[m[37m[44mPackage configuration[4;2H(0[30m[47mlqqqqqqqqqqqqqqqqqqqqqu(B[m(B[30m[47m [31mConfiguring libssl1.0.0:amd64[30m (0[30m[47mtqqqqqqqqqqqqqqqqqqqqqk[5;2Hx(B[m(B[30m[47m (0[30m[47mx(B[m(B[1m[37m[40m [6;2H(B[m(0[30m[47mx(B[m(B[30m[47m This release of OpenSSL fixes some security issues. Services will not (0[30m[47mx(B[m(B[1m[37m[40m [7;2H(B[m(0[30m[47mx(B[m(B[30m[47m use these fixes until they are restarted. Please note that restarting (0[30m[47mx(B[m(B[1m[37m[40m [8;2H(B[m(0[30m[47mx(B[m(B[30m[47m the SSH server (sshd) should not affect any existing connections. (0[30m[47mx(B[m(B[1m[37m[40m [9;2H(B[m(0[30m[47mx(B[m(B[30m[47m (0[30m[47mx(B[m(B[1m[37m[40m [10;2H(B[m(0[30m[47mx(B[m(B[30m[47m Please check the list of detected services that need to be restarted and (0[30m[47mx(B[m(B[1m[37m[40m [11;2H(B[m(0[30m[47mx(B[m(B[30m[47m correct it, if needed. The services names must be identical to the (0[30m[47mx(B[m(B[1m[37m[40m [12;2H(B[m(0[30m[47mx(B[m(B[30m[47m initialization script names in /etc/init.d and separated by spaces. No (0[30m[47mx(B[m(B[1m[37m[40m [13;2H(B[m(0[30m[47mx(B[m(B[30m[47m services will be restarted if the list is empty. (0[30m[47mx(B[m(B[1m[37m[40m [14;2H(B[m(0[30m[47mx(B[m(B[30m[47m (0[30m[47mx(B[m(B[1m[37m[40m [15;2H(B[m(0[30m[47mx(B[m(B[30m[47m Any service that later fails unexpectedly after this upgrade should be (0[30m[47mx(B[m(B[1m[37m[40m [16;2H(B[m(0[30m[47mx(B[m(B[30m[47m restarted. It is recommended to reboot this host to avoid any (0[30m[47mx(B[m(B[1m[37m[40m [17;2H(B[m(0[30m[47mx(B[m(B[30m[47m SSL-related trouble. (0[30m[47mx(B[m(B[1m[37m[40m [18;2H(B[m(0[30m[47mx(B[m(B[30m[47m (0[30m[47mx(B[m(B[1m[37m[40m [19;2H(B[m(0[30m[47mx(B[m(B[30m[47m [37m[41m<Ok>[30m[47m (0[30m[47mx(B[m(B[1m[37m[40m [20;2H(B[m(0[30m[47mx(B[m(B[30m[47m (0[30m[47mx(B[m(B[1m[37m[40m [21;2H(B[m(0[30m[47mmqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj(B[m(B[1m[37m[40m [22;3H [19;38HBuild timed out (after 81 minutes). Marking the build as aborted. Build was aborted Archiving artifacts ./build.sh: line 37: 6954 Terminated bundle exec veewee vbox build $appliance --nogui --auto + bundle exec veewee vbox halt systemvm64template Waiting for ssh login on 127.0.0.1 with user root to sshd on port => 7222 to work, timeout=10000 sec . Executing command: echo 'halt -p' > /tmp/shutdown.sh Waiting for ssh login on 127.0.0.1 with user root to sshd on port => 7222 to work, timeout=10000 sec . Executing command: chmod +x /tmp/shutdown.sh Waiting for ssh login on 127.0.0.1 with user root to sshd on port => 7222 to work, timeout=10000 sec . Executing command: /tmp/shutdown.sh Broadcast message from root@systemvm (pts/2) (Wed Apr 9 20:13:56 2014): The system is going down for system halt NOW! -- This message was sent by Atlassian JIRA (v6.2#6252)