qemu: tar: Unexpected EOF in archive in copyup()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
autopkgtest (Debian) |
Fix Released
|
Unknown
|
|||
autopkgtest (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Sometimes MAAS adt tests fail to copy artifacts from the testbed to the host.
adt-run1: testbed executing test finished with exit status 0
adt-run2: >> copyup /tmp/adt-
adt-run2: << ok
adt-run2: >> copyup /tmp/adt-
adt-run2: << ok
adt-run: & ubtree0t-
ubtree0t-
adt-run2: >> copyup /tmp/adt-
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
qemu: terminating on signal 15 from pid 353
<VirtSubproc>: failure: copyup destination failed, status 2
adt-run1: ** bomb unexpected eof from the testbed
adt-run1: ** stop
adt-run1: ** close, scratch=
adt-run2: >> close
adt-run1: ** bomb cannot send to testbed: ['IOError: [Errno 32] Broken pipe\n']
adt-run1: ** stop
adt-run: testbed failed: cannot send to testbed: ['IOError: [Errno 32] Broken pipe\n']
adt-run1: ** stop
adt-run2: / tests-tree rmtree /home/ubuntu/
Build step 'Execute shell' marked build as failure
Full log can be found here: http://
This looks like bug 1317358 but the autopkgtest version used in the MAAS lab includes the fix for it, so it might be a new root cause.
summary: |
- tar: Unexpected EOF in archive in copyup() + qemu: tar: Unexpected EOF in archive in copyup() |
Changed in autopkgtest (Ubuntu): | |
status: | Triaged → Fix Committed |
Changed in autopkgtest (Debian): | |
status: | Unknown → New |
Changed in autopkgtest (Debian): | |
status: | New → Fix Released |
Indeed I'm aware of it, it occasionally happens on other autopkgtest runs, too. It's just exceptionally hard to reproduce locally. I already spent some hours trying to understand and reproduce the problem, so far not very successfully :-(