Red Hat Bugzilla – Bug 994181
REST: Cannot clone repository if it was cloned and deleted previously
Last modified: 2014-08-06 16:16:24 EDT
Created attachment 783408 [details]
clone exception response
Description of problem:
I'm currently unable to perform following scenario that is important for test automation: as a test setup I need to delete a repository and clone it again to get it into clean state. I perform these steps:
1. delete the repository using DELETE rest/repositories/$REPO
2. rm -rf .niogit/$REPO.git
3. clone again using POST rest/repositories/ + JSON data containing repo URL and name
On the first run steps 1. and 2. have no effect and step 3. is successful, repo is cloned. Tests work with $REPO and create some commits. When the sequence is carried out again, step 1. removes $REPO from system.git, but doesn't touch .niogit/$REPO.git. That is done in step 2. After that, a fresh clone of $REPO should be created but the REST call throws exception this time.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. clone a repository as $REPO
2. delete it
3. clear .niogit/$REPO.git
4. clone it again
XML response with exception stack trace
JSON data with successful status
1. REST clone
2. REST delete
3. stop server
4. rm -rf
5. start server
6. REST clone
Bug fixed on master, pushing now to 6.0.x and 0.3.x
Marked as requiring a release note for the beta release.
Please add relevant information we need customers to be aware of to the doc text box above.
Works perfect now.