Test/fix production ODCS #7144
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
5 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Infrastructure/fedora-infrastructure#7144
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?
We're preparing to deploy the Flatpak building code that has been tested in staging to production. This will require a working ODCS instance. The last build on https://odcs.fedoraproject.org/api/1/composes/ never succeeded, so it's probably not working at the moment - though it's possible that the fixes that were done for staging fixed production as a side-effect. I'm thinking the first thing to do would be to try a fresh compose.
cc: @jkaluza @ralph
Metadata Update from @mizdebsk:
I talked with @otaylor and others on Flock about ODCS in fedora and I will try to be more responsible to ODCS in Fedora.
The reason why ODCS prod is not up to date is that nobody really used it, because the original use-case of testing modules is blocked on #6672. I should still keep it up to date even with nobody using it, but my motivation and time to do that was quite low. Anyway, I will try doing better now when there is actually use-case for ODCS in Fedora. Sorry for the current situation.
I will update it next week once Flock is over.
I wanted to fix prod ODCS and started with testing it and it seems to be working properly. There is not the latest greatest version deployed, but it seems to work.
@otaylor, @cverna: Can you try it yourself and tell me in case there are some issues?
Metadata Update from @kevin:
Thanks for doing the testing, @jkaluza! - I don't think that I have the permissions to do further testing manually, but the test module build you did seems to have generated the correct content. I think we can close this and open a new issue if something turns up when we try to run OSBS against it.
Metadata Update from @otaylor:
\ó/