MBS: rebuild appears to be stuck #7746
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
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: infrastructure/fedora-infrastructure#7746
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?
Previously this failed with "too many files" so I cancelled and resubmitted.
Can you try again now? I restarted fedmsg-hub on mbs-backend01.
I did:
@jkaluza Can you look?
Metadata Update from @kevin:
I know it's not ideal, but you could cancel the build, bump the git commit of the modulemd file, and then submit, if you're still having issues. It's likely MBS didn't handle the "too many files open" error gracefully and is in a weird state.
@orion any luck with what @mprahl said there?
I see a successfull build here: https://release-engineering.github.io/mbs-ui/module/4108
So, closing this... if there's still an issue or further action is needed, please let us know.
Metadata Update from @kevin: