Uploading files to a Koji Content Generator build fails #7838
Labels
No labels
announcement
authentication
automate
aws
backlog
blocked
bodhi
ci
Closed As
Duplicate
Closed As
Fixed
Closed As
Fixed with Explanation
Closed As
Initiative Worthy
Closed As
Insufficient data
Closed As
Invalid
Closed As
Spam
Closed As
Upstream
Closed As/Will Not
Can Not fix
cloud
communishift
copr
database
deprecated
dev
discourse
dns
downloads
easyfix
epel
factory2
firmitas
gitlab
greenwave
hardware
help wanted
high-gain
high-trouble
iad2
koji
koschei
lists
low-gain
low-trouble
mbs
medium-gain
medium-trouble
mini-initiative
mirrorlists
monitoring
Needs investigation
notifier
odcs
OpenShift
ops
OSBS
outage
packager_workflow_blocker
pagure
permissions
Priority
Needs Review
Priority
Next Meeting
Priority
🔥 URGENT 🔥
Priority
Waiting on Assignee
Priority
Waiting on External
Priority
Waiting on Reporter
rabbitmq
rdu-cc
release-monitoring
releng
repoSpanner
request-for-resources
s390x
security
SMTP
src.fp.o
staging
taiga
unfreeze
waiverdb
websites-general
wiki
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Infrastructure/fedora-infrastructure#7838
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
When MBS finishes building all the module components, it creates a content generator build in Koji representing the module build. As part of this process, it uploads a number of text files, such as the modulemd file per architecture. MBS is failing to upload these, and the exception from the Python Koji library is not providing any hints:
GenericError: File upload failed: mbs/1558714965.779766.4363/modulemd.aarch64.txt
Could you please take a look at the Koji logs to see if there is an issue on the Koji side? This is happening on every new module build.
/cc @mbooth
I'll check Koji logs.
Metadata Update from @mizdebsk:
Koji logs indicate that the upload succeeded. HTTP code 200.
The uploaded file is indeed available at https://kojipkgs.fedoraproject.org/work/mbs/1558714965.779766.4363/modulemd.aarch64.txt
Is there anything else I can help with to debug the issue?
Metadata Update from @mizdebsk:
After 25 minutes or so, I restarted MBS and tried again and it worked. I'm not sure if it was coincidence or not. I'll have @mbooth try his module build again. If successful, I'll close the ticket.
I just tried it again and the problem has come back. Any ideas?
I've switched MBS to use fast upload method. Lets see if this helps.
@mizdebsk that solved the issue. Thank you!
Metadata Update from @mprahl: