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.

Sign up for GitHub

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

Jump to bottom

Bodhi must be restarted after using bodhi-manage-releases to create a new release #2177

Closed
bowlofeggs opened this issue Feb 27, 2018 · 4 comments · Fixed by #3345
Closed

Bodhi must be restarted after using bodhi-manage-releases to create a new release #2177

bowlofeggs opened this issue Feb 27, 2018 · 4 comments · Fixed by #3345
Labels
API Issues related to Bodhi's REST API Critical We can't go on living in this sqalor, drop everything and fix it! reliability Issues pertaining to Bodhi's reliability Server CLI Issues pertaining to Bodhi's server command line tools

Comments

@bowlofeggs
Copy link
Contributor

I noticed today that I needed to restart Bodhi after using bodhi-manage-releases to create a new Release object before I could create an update that used tags from that Release. I think this is due to some permanent caching in the Release model code. We should probably have changes to releases reset those caches.
@bowlofeggs bowlofeggs added API Issues related to Bodhi's REST API Server CLI Issues pertaining to Bodhi's server command line tools reliability Issues pertaining to Bodhi's reliability labels Feb 27, 2018
@bowlofeggs bowlofeggs added the Critical We can't go on living in this sqalor, drop everything and fix it! label Aug 29, 2018
@bowlofeggs
Copy link
Contributor Author

Since bodhi-manage-releases is now deprecated, this should be done in bodhi releases edit/create instead.

@bowlofeggs
Copy link
Contributor Author

Note that this one will be difficult to do because Bodhi uses multiple server processes, and they must all be notified to clear their caches when releases are edited or created. There isn't currently an infrastructure in place to do this.

@bowlofeggs
Copy link
Contributor Author

We will need to either start using a caching server for Bodhi's processes, or will need to make the queries efficient so we don't need a cache at all.

@bowlofeggs
Copy link
Contributor Author

I believe that @nphilipp might be interested in solving this problem.

@sebwoj sebwoj mentioned this issue Jun 14, 2019
Closed
sebwoj added a commit to sebwoj/bodhi that referenced this issue Jun 23, 2019
@sebwoj
Make Bodhi able to clear models.Release._all_releases cache
fe6e24d 
fix fedora-infra#2177

Signed-off-by: Sebastian Wojciechowski <[email protected]>
@sebwoj sebwoj mentioned this issue Jun 23, 2019
Merged
sebwoj added a commit to sebwoj/bodhi that referenced this issue Jun 28, 2019
@sebwoj
Make Bodhi able to clear models.Release._all_releases cache
a5a320e 
fix fedora-infra#2177

Signed-off-by: Sebastian Wojciechowski <[email protected]>
@mergify mergify bot closed this as completed in #3345 Jul 9, 2019
mergify bot pushed a commit that referenced this issue Jul 9, 2019
@sebwoj @mergify
Make Bodhi able to clear models.Release._all_releases cache
b2ff431 
fix #2177

Signed-off-by: Sebastian Wojciechowski <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
API Issues related to Bodhi's REST API Critical We can't go on living in this sqalor, drop everything and fix it! reliability Issues pertaining to Bodhi's reliability Server CLI Issues pertaining to Bodhi's server command line tools
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Make Bodhi able to clear models.Release._all_releases cache sebwoj/bodhi
1 participant
@bowlofeggs