Project

General

Profile

Bug #8742

calamari build: some failures aren't reported by vagrant ssh

Added by Warren Usui about 7 years ago. Updated about 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Backend (packaging/deployment)
Target version:
% Done:

0%

Source:
Development
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Crash signature (v1):
Crash signature (v2):

Description

Running

./ice_repo_tgz.py -v -b v0.81 -o centos6.5

Resulted in:

.
.
.
Saving Primary metadata
Saving file lists metadata
Saving other metadata
INFO:ice_repo_targz:Signing repo: 
INFO:ice_repo_targz:getting calamari-minions packages
Downloaded: 23,415/23,415 KiB 100.00% @ 6,838 KiB/sec  ETA: 0h0m0s      
{'filepat': 'calamari-repo.*tar.gz', 'server': 'jenkins-calamari.front.sepia.ceph.com', 'pkgext': 'rpm', 'path': '/var/lib/jenkins/jobs/calamari-server-{distro}/lastSuccessful/archive', 'packages': None, 'method': 'get_pkgs_from_repo_tarball'}
Traceback (most recent call last):
  File "./ice_repo_tgz.py", line 1201, in <module>
    main()
  File "./ice_repo_tgz.py", line 1198, in main
    pull_projects(args)
  File "./ice_repo_tgz.py", line 1162, in pull_projects
    get_from_sourcedesc(minion_pkgs[disttype], operating_system, disttype)
  File "./ice_repo_tgz.py", line 1099, in get_from_sourcedesc
    source['pkgext'], workfolder)
  File "./ice_repo_tgz.py", line 988, in get_pkgs_from_repo_tarball
    raise RuntimeError('repo_tarball not found on sftp server')
RuntimeError: repo_tarball not found on sftp server

I can provided the entire output (about 600 lines) if needed.

History

#1 Updated by Warren Usui about 7 years ago

  • Assignee set to Dan Mick

#2 Updated by Dan Mick about 7 years ago

  • Category set to Backend (packaging/deployment)
  • Status changed from New to 12
  • Priority changed from Normal to Low
  • Source changed from other to Development

The build had a failure midway through while trying to make el6 in repobuild which was not transmitted out to a failure of vagrant ssh. grr. Will have to investigate what failures are caught and what are not more deeply at some point.

#3 Updated by Dan Mick about 7 years ago

  • Subject changed from ICE: Hmmm. tarball builds on Centos6.5 fail to build. to calamari build: some failures aren't reported by vagrant ssh
  • Category deleted (Backend (packaging/deployment))
  • Priority changed from Low to Normal
  • Source changed from Development to other

The build had a failure midway through while trying to make el6 in repobuild which was not transmitted out to a failure of vagrant ssh. grr. Will have to investigate what failures are caught and what are not more deeply at some point.

#4 Updated by Dan Mick about 7 years ago

  • Status changed from 12 to In Progress

#5 Updated by Dan Mick about 7 years ago

I have test shell code to look for Failed: strings that seems to work well enough; I just need to apply it to the other builds.

#6 Updated by Dan Mick about 7 years ago

Pushed changes to all the builds, more or less like this:

-vagrant ssh -c 'sudo salt-call --local state.highstate'
+vagrant ssh -c 'sudo salt-call --local state.highstate' | tee /tmp/${BUILD_TAG}.out
+errs=$(sed --regexp-extended -n 's/^Failed:[[:space:]]+([[:digit:]]+)/\1/p' < /tmp/${BUILD_TAG}.out)
+rm /tmp/${BUILD_TAG}.out
+if [ $errs != 0 ] ; then echo "$errs HIGHSTATE ERRORS, BUILD FAILED"; exit 1; fi

See commit 6e1afd0d8ab734a472a820a415daa43e8a7a4d3a in github.com/ceph/jenkins-jobs

#7 Updated by Dan Mick about 7 years ago

  • Category set to Backend (packaging/deployment)
  • Status changed from In Progress to Resolved
  • Target version set to 1.3-dev4
  • Source changed from other to Development

Also available in: Atom PDF