Scout24/yum-repo-server

Delete repository not working

Closed this issue · 5 comments

When I try to delete just freshly created repo all seems to go fine.

But in case repository contains rpms or even only metadata, then
I get ok response for delete rest call, but repository kind of stays.
GUI will still be listing it
When trying to click the link you get: HTTP Status 404 - Repository not found.
Recreating repo with same name shows old data still being present.

How long did you wait? It could be that the repo only disappears after the
next maintenance run or something like that.

On 25 September 2013 15:03, owueffsdaf notifications@github.com wrote:

When I try to delete just freshly created repo all seems to go fine.

But in case repository contains rpms or even only metadata, then
I get ok response for delete rest call, but repository kind of stays.
GUI will still be listing it
When trying to click the link you get: HTTP Status 404 - Repository not
found.
Recreating repo with same name shows old data still being present.


Reply to this email directly or view it on GitHubhttps://github.com//issues/27
.

I did not wait.
I have tried to restart the server to see if there is some kind of caching.
I will try to wait now. Just now send a delete request on a repo with metadata and single rpm. I will update you.

You are right. I have to wait. Repository disappears after some time. Do not know exactly how long though. Maybe 10/20 min.
If I recreate repository with a same name as the deleted repo. then it comes back up empty as expected.

All is fine. Sorry for the noise.

We should probably document this behaviour. It is actually intended so that
the repo survives the typical metadata_expiration (we use 30s for that).

On 25 September 2013 16:37, owueffsdaf notifications@github.com wrote:

You are right. I have to wait. Repository disappears after some time. Do
not know exactly how long though. Maybe 10/20 min.
If I recreate repository with a same name as the deleted repo. then it
comes back up empty as expected.

All is fine. Sorry for the noise.


Reply to this email directly or view it on GitHubhttps://github.com//issues/27#issuecomment-25091107
.

Makes complete sense.