-
Notifications
You must be signed in to change notification settings - Fork 193
-
Notifications
You must be signed in to change notification settings - Fork 193
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
Add logs at every place that expires buildroot overrides #3060
Labels
Buildroot Override
Issues related to buildroot overrides
EasyFix
These are good issues to get started with if you are new to the project
High priority
These issues are higher priority than normal
Comments
bowlofeggs
added
EasyFix
These are good issues to get started with if you are new to the project
Buildroot Override
Issues related to buildroot overrides
High priority
These issues are higher priority than normal
labels
Mar 14, 2019
I'll take a shot at this before my PTO next week. |
Looks like I need to be added to the org or project before I can assign this to myself. |
nphilipp
added a commit
to nphilipp/bodhi
that referenced
this issue
Mar 15, 2019
This lets us debug BROs unexpectedly getting untagged in Koji easier. Fixes fedora-infra#3060 Signed-off-by: Nils Philippsen <nils@redhat.com>
bowlofeggs
pushed a commit
to nphilipp/bodhi
that referenced
this issue
Mar 21, 2019
This lets us debug BROs unexpectedly getting untagged in Koji easier. Fixes fedora-infra#3060 Signed-off-by: Nils Philippsen <nils@redhat.com>
This feature is planned for inclusion in the upcoming 4.0.0 release: #3221 |
Bodhi 4.0.0 beta is built and deployed to staging: https://copr.fedorainfracloud.org/coprs/bowlofeggs/bodhi-pre-release |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Buildroot Override
Issues related to buildroot overrides
EasyFix
These are good issues to get started with if you are new to the project
High priority
These issues are higher priority than normal
Some users have been having trouble with buildroot overrides getting unexpectedly untagged in Koji, and according to Koji the Bodhi user is the one untagging it. Unfortunately, Bodhi does not currently emit log messages when
BuildrootOverride.expire()
is called, so it is not easy to tell which code path is responsible for this.We should find all the calls to
BuildrootOverride.expire()
and add log messages to explain why it is being called, for each one. This way we will have more useful debugging information in the future.The text was updated successfully, but these errors were encountered: