Unable to delete Git repositories due to 'Repository currently not available'
Asked by Config Sync CI Bot:

I got the '***Repository currently not available'*** failure when trying to delete a repository using cURL:

```
$ curl -sX DELETE --user user:password https://api.bitbucket.org/2.0/repositories/workspace-id/repo
```

```
Repository currently not available.
```

The UI page for the repository is not responding: <https://bitbucket.org/workspace-id/repo/src>. It spins forever.

When I refreshed the page, Bitbucket seemed to try to create a repository.

It feels like the repository was partially deleted.

Is there a way to show the actual status of this repository, or force-delete this repository?


Answers:
author: Theodora Boudale
body: Hi [@Config Sync CI Bot](/t5/user/viewprofilepage/user-id/5360064) and welcome to the community!

It looks like the repo deletion task failed and this repo is now stuck in CREATING mode with 0 bytes of data.

You won't be able to delete this repo, but I can delete it for you if you give me permission since you are an admin.

Please let me know if I have your permission to delete that repo.

Just a heads up, I removed the repo URL and screenshots (since they show the repo URL) from your post to protect your privacy.

Kind regards,  
Theodora

comments: author: Config Sync CI Bot
body: Hi Theodora,

Thank you for your help! Could you please provide your username so I can grant you permission to delete the repo?

Also, I'd like to understand the root cause of the deletion task failure, as this has happened a few times before. If it occurs again, how can we request a deletion?

Thank you for your assistance!


author: Theodora Boudale
body: Hi!

You don't need to grant me access to the workspace for me to delete the repo. I can do it from the backend, I just need you to state that you give me permission to delete this repo, before I proceed.

Regarding the root cause, this repo was deleted more than 30 days ago, and due to our logs retention policy there are no logs for me to check. If this issue occurs again, could you please reach out then and provide a) the date and approximate time (in UTC, if you don't want to add a timezone) that you ran the API call and b) a few letters of the repo name so I can identify it among others you may have deleted during the same time? I will then check our logs for any further info.

If this ever occurs again, you can create a question in community like you did with this question and request a deletion. We have Atlassian staff, myself included, checking community.

Kind regards,  
Theodora


author: Config Sync CI Bot
body: Hi Theodora,

Thanks for the reply. Yes, you have my permission to delete the repo.

Sure, if it happens next time, I would reach out with all the context you requested.

Thanks!


author: Theodora Boudale
body: Hi,

Thank you for the confirmation, I went ahead and deleted that repository.

Please feel free to reach out if this ever occurs again or if you need anything else!

Kind regards,  
Theodora


author: Config Sync CI Bot
body: Hi Theodora,

This issue happened again when attempting to delete repo \`bookstorereposynce0228a\` in the \`config-sync-ci-20240328\` workspace.

Below listed some timestamps for the deletion:  
* 2024-05-30 02:06:00.01638308 +0000 UTC Deleting the following repos: bookstorereposynce0228a....
* 2024-05-30 02:06:00.167536217 +0000 UTC ERROR: Repository currently not available.  
Before deleting that repo, there was another error occurred while deleting other repos:  
* 2024-05-29 22:05:06.728802914 +0000 UTC Deleting the following repos: configmanagementsystemrootsync18c9a74...., configmanagementsystemrootsync345890....., configmanagementsystemrootsync0c499a...., configmanagementsystemrootsyncc569d9....., bookstorereposync400c.... testnsrstest1d634...., testnsrstest2ddab.... configmanagementsystemroottest3f387ae...., testnsrstestaf76035...., configmanagementsystemrr174dd....
* 2024-05-29 22:05:09.383426365 +0000 UTC ERROR: {"type": "error", "error": {"message": "You may not have access to this repository or it no longer exists in this workspace. If you think this repository exists and you have access, make sure you are authenticated."}}; {"type": "error", "error": {"message": "You may not have access to this repository or it no longer exists in this workspace. If you think this repository exists and you have access, make sure you are authenticated."}}; {"type": "error", "error": {"message": "You may not have access to this repository or it no longer exists in this workspace. If you think this repository exists and you have access, make sure you are authenticated."}}; {"type": "error", "error": {"message": "You may not have access to this repository or it no longer exists in this workspace. If you think this repository exists and you have access, make sure you are authenticated."}}; {"type": "error", "error": {"message": "You may not have access to this repository or it no longer exists in this workspace. If you think this repository exists and you have access, make sure you are authenticated."}}; {"type": "error", "error": {"message": "You may not have access to this repository or it no longer exists in this workspace. If you think this repository exists and you have access, make sure you are authenticated."}}; {"type": "error", "error": {"message": "You may not have access to this repository or it no longer exists in this workspace. If you think this repository exists and you have access, make sure you are authenticated."}}  
All the repos on the list seemed to be deleted successfully. Hence, I'm not sure if they are related.  
Please take a look and let us know what might cause the deletion error. Thanks in advance!


author: Config Sync CI Bot
body: Hi Theodora, the issue happened again. I posted another question with more details: <https://community.atlassian.com/t5/Bitbucket-questions/Unable-to-delete-Git-repositories-due-to-Repository-currently/qaq-p/2713100#M104729>.

Please take a look and let us know what might cause the deletion issue. Thanks!


Tags: bitbucket-cloud

cloud