Started by user Joao Pina Building remotely on sl6-nova-347 (sl6) in workspace /tmp/workspace/frontier-squid Cloning the remote Git repository Cloning repository https://github.com/egi-qc/umd-verification > git init /tmp/workspace/frontier-squid # timeout=10 Fetching upstream changes from https://github.com/egi-qc/umd-verification > git --version # timeout=10 > git fetch --tags --progress https://github.com/egi-qc/umd-verification +refs/heads/*:refs/remotes/origin/* > git config remote.origin.url https://github.com/egi-qc/umd-verification # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url https://github.com/egi-qc/umd-verification # timeout=10 Fetching upstream changes from https://github.com/egi-qc/umd-verification > git fetch --tags --progress https://github.com/egi-qc/umd-verification +refs/heads/*:refs/remotes/origin/* > git rev-parse refs/remotes/origin/redux^{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/redux^{commit} # timeout=10 Checking out Revision db2a7630cc86a63f40ac1c317c2db56d4d46026d (refs/remotes/origin/redux) > git config core.sparsecheckout # timeout=10 > git checkout -f db2a7630cc86a63f40ac1c317c2db56d4d46026d > git rev-list cc7128433a5f9d5ac86b060e7cb97024f84c6170 # timeout=10 [frontier-squid] $ /bin/sh -xe /tmp/hudson7831570553951951001.sh + [[ sl6 == sl6* ]] + sudocmd=rvmsudo ++ ./bin/jenkins/parse_repos.sh http://admin-repo.egi.eu/sw/unverified/umd-4.cernfrontier.squid.sl6.x86_64/3/5/24/repofiles/CERNFRONTIER.squid.sl6.x86_64.repo + Verification_repository=repository_file_1=http://admin-repo.egi.eu/sw/unverified/umd-4.cernfrontier.squid.sl6.x86_64/3/5/24/repofiles/CERNFRONTIER.squid.sl6.x86_64.repo + '[' full-deployment == installation-only ']' + rvmsudo fab frontier-squid:umd_release=4,repository_file_1=http://admin-repo.egi.eu/sw/unverified/umd-4.cernfrontier.squid.sl6.x86_64/3/5/24/repofiles/CERNFRONTIER.squid.sl6.x86_64.repo,log_path=logs Warning: can not check `/etc/sudoers` for `secure_path`, falling back to call via `/usr/bin/env`, this breaks rules from `/etc/sudoers`. Run: export rvmsudo_secure_path=1 to avoid the warning, put it in shell initialization file to make it persistent. In case there is no `secure_path` in `/etc/sudoers`. Run: export rvmsudo_secure_path=0 to avoid the warning, put it in shell initialization file to make it persistent. [INFO] Using UMD 4 release repository [INFO] Using UMD verification repository file: ['http://admin-repo.egi.eu/sw/unverified/umd-4.cernfrontier.squid.sl6.x86_64/3/5/24/repofiles/CERNFRONTIER.squid.sl6.x86_64.repo'] UMD verification tool ===================== Quality criteria: http://egi-qc.github.io Codebase: https://github.com/egi-qc/umd-verification Path locations | | log_path logs | yaim_path etc/yaim | puppet_path etc/puppet Production repositories | | umd_release_pkg http://repository.egi.eu/sw/production/umd/4/sl6/x86_64/updates/umd-release-4.0.0-1.el6.noarch.rpm | igtf_repo None [INFO] Using the following repository files + http://admin-repo.egi.eu/sw/unverified/umd-4.cernfrontier.squid.sl6.x86_64/3/5/24/repofiles/CERNFRONTIER.squid.sl6.x86_64.repo [localhost] local: sudo -E mkdir -p /etc/grid-security/certificates [localhost] local: sudo -E chown root:root /etc/grid-security [localhost] local: sudo -E chmod 0755 /etc/grid-security [INFO] Generating own certificates [localhost] local: sudo -E mkdir -p /root/UMDVerificationOwnCA [localhost] local: sudo -E openssl req -x509 -nodes -days 1 -newkey rsa:2048 -out ca.pem -outform PEM -keyout ca.key -subj '/DC=es/DC=UMDverification/CN=UMDVerificationOwnCA' [localhost] local: sudo -E openssl x509 -noout -hash -in ca.pem [localhost] local: sudo -E cp ca.pem /etc/grid-security/certificates/0d2a3bdd.0 [localhost] local: sudo -E echo "01" > crlnumber [localhost] local: sudo -E touch index.txt [localhost] local: sudo -E openssl ca -config openssl.cnf -gencrl -keyfile ca.key -cert ca.pem -out crl.pem [localhost] local: sudo -E cp crl.pem /etc/grid-security/certificates/0d2a3bdd.r0 [localhost] local: sudo -E openssl req -newkey rsa:2048 -nodes -sha1 -keyout cert.key -keyform PEM -out cert.req -outform PEM -subj '/DC=es/DC=UMDverification/CN=sl6-nova-347.privatevlan.cloud.ifca.es' -config openssl.cnf [localhost] local: sudo -E openssl x509 -req -in cert.req -CA ca.pem -CAkey ca.key -CAcreateserial -extensions v3_req -extfile openssl.cnf -out cert.crt -days 1 [localhost] local: sudo -E chmod 600 cert.key [localhost] local: sudo -E cp cert.key /etc/grid-security/hostkey.pem [INFO] Private key stored in '/etc/grid-security/hostkey.pem' (with 600 perms). [localhost] local: sudo -E cp cert.crt /etc/grid-security/hostcert.pem [INFO] Public key stored in '/etc/grid-security/hostcert.pem'. [INFO] Running configuration [localhost] local: sudo -E rpm --quiet -q puppetlabs-release [FAIL] Command execution has failed (reason: "") (action: no exit) [localhost] local: sudo -E rpm -ivh https://yum.puppetlabs.com/puppetlabs-release-el-6.noarch.rpm [localhost] local: sudo -E yum -y install puppet [localhost] local: sudo -E mkdir /etc/puppet/hieradata [INFO] Adding hiera parameter files: ['umd'] [localhost] local: librarian-puppet [localhost] local: librarian-puppet install --clean --path=/etc/puppet/modules --verbose [INFO] Log directory 'logs' has been created. [localhost] local: puppet config print modulepath [localhost] local: puppet apply --verbose --debug --modulepath /etc/puppet/modules:/usr/share/puppet/modules etc/puppet/frontier_squid.pp --detail-exitcodes [FAIL] Command execution has failed (reason: "") (action: no exit) (log: ['qc_conf.stdout']) [INFO] Puppet execution ended successfully (some warnings though, check logs) [[QC_SEC_2: SHA-2 Certificates Support]] [[QC_SEC_5: World Writable Files]] [localhost] local: sudo -E find / -not \( -path "/proc" -prune \) -not \( -path "/sys" -prune \) -type f -perm -002 -exec ls -l {} \; [OK] Found no world-writable file. [[QC_INFO_1: GlueSchema 1.3 Support]] [NA] Product does not publish information through BDII. [[QC_INFO_2: GlueSchema 2.0 Support]] [NA] Product does not publish information through BDII. [[QC_INFO_3: Middleware Version Information]] [NA] Product does not publish information through BDII. [[QC_MON_1: Service Probes]] [NA] Product cannot be tested by Nagios. [[QC_FUNC_1: Basic Funcionality Test.]] [INFO] Probe 'Frontier squid cache test.' [localhost] local: su jenkins -c "./bin/frontier-squid/fnget.sh " 2>&1 [INFO] Command 'su jenkins -c "./bin/frontier-squid/fnget.sh "' ran successfully [OK] Basic functionality probes ran successfully. [[QC_FUNC_2: New features/bug fixes testing.]] [NA] No definition found for QC_FUNC_2. Archiving artifacts Finished: SUCCESS