-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tree: promote changes from testing-devel at 44951ad75164 #198
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All looks like expected changes from development so far; LGTM!
Hm, something going wrong with lockfiles? |
coreos-koji-tagger fell over and those builds weren't tagged into the pool. I've tagged them all in, which fixed |
I had run the tagger twice, not realizing that there's a delay between adding a package to the intermediate tag and koji adding them to the target tag. The result was two sets of tagging tasks, which apparently spawned repo regeneration tasks that raced with each other and resulted in a stale repo. To address this, |
Do you have any logs from it failing? I'm looking at the logs now but it looks like the container was restarted and previous logs are gone. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Nope. I don't actually seem to have access to Fedora OpenShift. 🙁 |
Ahh yup, that's https://pagure.io/koji/issue/1630. |
This should help. https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=371f02c8d617e2d0f698fe63c2aa56953f18bdd0 Next time you should be able to browse https://os.fedoraproject.org/console/project/coreos-koji-tagger/overview |
No description provided.