uploading ticket fails with broken pipe (does not retry on broken connection to Swift)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu CI Engine |
Fix Released
|
High
|
Ursula Junque |
Bug Description
.venv/bin/ubuntu-ci create_ticket -t "Testing kernel" -d "A ticket for Testing kernel" -a linux-image-
failed with:
ubuntu-ci ERROR Unexpected exception
Traceback (most recent call last):
File "/home/
args.func(args)
File "/home/
new_
File "/home/
subticket.
File "/home/
location = upload_
File "/home/
location = ds.put_
File "/home/
content_
File "/home/
conn.
File "/usr/lib/
self.
File "/usr/lib/
v = self.send(
File "/usr/lib/
v = self._sslobj.
error: [Errno 32] Broken pipe
Note that the traceback is similar to bug #1289567 but for a different purpose.
Here, I was trying to create a ticket for kernel testing.
Changed in uci-engine: | |
assignee: | nobody → Ursula Junque (ursinha) |
importance: | Undecided → High |
status: | New → Confirmed |
no longer affects: | ubuntu-ci-services-itself |
summary: |
- uploading ticket fails with broken pipe + uploading ticket fails with broken pipe (does not retry on broken + connection to Swift) |
Changed in uci-engine: | |
milestone: | none → uce-1 |
For this specific case uploading >100M seems like:
- a blocker with my actual network connection,
- a pain for anyone wanting to create such a ticket.
I thought there was a way to let launchpad find the source tarball itself but I don't know the specifics.
If that was possible then creating the ticket may be possible with uploading only the .dsc and .source_changes which have far more reasonable sizes ?