Skip to content
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

Merged
merged 1 commit into from
Oct 15, 2019
Merged

tree: promote changes from testing-devel at 44951ad75164 #198

merged 1 commit into from
Oct 15, 2019

Conversation

bgilbert
Copy link
Contributor

No description provided.

Copy link
Member

@cgwalters cgwalters left a 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!

@cgwalters
Copy link
Member

error: Packages not found: fuse-overlayfs, kernel-core, microcode_ctl, openssl, whois-nls

Hm, something going wrong with lockfiles?

@bgilbert
Copy link
Contributor Author

coreos-koji-tagger fell over and those builds weren't tagged into the pool. I've tagged them all in, which fixed fuse-overlayfs, but the others are still failing for some reason.

@bgilbert
Copy link
Contributor Author

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, koji regen-repo didn't work for me, so I untagged and retagged a package from coreos-pool and the resulting regen task fixed the repo.

@dustymabe
Copy link
Member

coreos-koji-tagger fell over and those builds weren't tagged into the pool.

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.

Copy link
Member

@dustymabe dustymabe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@bgilbert
Copy link
Contributor Author

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.

Nope. I don't actually seem to have access to Fedora OpenShift. 🙁

@bgilbert bgilbert merged commit 3cf8e89 into coreos:testing Oct 15, 2019
@bgilbert bgilbert deleted the testing branch October 15, 2019 02:43
@jlebon
Copy link
Member

jlebon commented Oct 15, 2019

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.

Ahh yup, that's https://pagure.io/koji/issue/1630.

@dustymabe
Copy link
Member

Nope. I don't actually seem to have access to Fedora OpenShift. slightly_frowning_face

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

dustymabe pushed a commit to jbtrystram/fedora-coreos-config that referenced this pull request Apr 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants