(Already reported Issue re-created as someone marked it as 'invalid' in the beginning of 2016 and I have a suspicion that it might be ignored for that reason by the staff)
Steps to repeat
Unfortunately I have not found a way to repeat this, but I could provide one such private repository name in your system: vaimo/module-cms
Testing creating, deleting, re-creating with random new repository name (for example: test123), seems to work just fine, which makes me wonder if there's some kind of cache/index that BitBucket uses that just takes time to sync up with the reality?
Trying to clone the before-mentioned problem-child does result in expected behaviour:
hg clone ssh://firstname.lastname@example.org/vaimo/module-cms remote: repository does not exist. abort: no suitable response from remote hg!
But this is what one gets when trying to create it:
- Before the deletion, the repository had a "remote: abort: abandoned transaction found!" BitBucket response, which I decided to quickly resolve (seeing that it's usually fixed manually by the staff) by re-creating the whole repository (which used to work just fine).
- Deletion did not result in any visible errors (although the user was not redirected to general Team's repository list as they usually are when removing a repository)
- The name still shows up in the search as well (indexing lag?)