Deleted repository can not be re-created.

Issue #14486 open
Allan Paiste
created an issue

(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://
remote: repository does not exist.
abort: no suitable response from remote hg!

But this is what one gets when trying to create it:

Screen Shot 2017-07-05 at 11.59.01.png

Additional facts

  1. 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).
  2. 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)
  3. The name still shows up in the search as well (indexing lag?)

Comments (13)

  1. Allan Paiste reporter

    Contacted the support team & got the name back. Thanks you! Would still be cool to force-delete it or to get more information on the failure (and/or some interactivity to the whole process to avoid spamming the BB support with similar minor things)

  2. Log in to comment