Description of problem: Firstly, I created an app with name "cake", and enable jenkins to it. Then I delete this app, and create another app with the same name "cake". After enable jenkins to the new app , I got a build failture. The log message shown as follows: "..... Cloning the remote Git repository Cloning repository origin ERROR: Error cloning remote repo 'origin' : Could not clone ssh://a5a17affb84f4306914050b02f8efe43.com/~/git/cake.git/ ERROR: Cause: Error performing command: git clone --progress -o origin ssh://a5a17affb84f4306914050b02f8efe43.com/~/git ......" Version-Release number of selected component (if applicable): devenv_2109,production How reproducible: always Steps to Reproduce: 1.Create app named "cake". 2.Enable jenkins to the app with jenkins server named "jenkins". 3.Delete the app. 4.Create a new app ,and enable jenkins to it in the jenkins server "jenkins" 5.Build the new app in jenkins server. Actual results: Build failed . Expected results: It should build successfully. Additional info: I have looked up the configure file of the app in jenkins server, and found that the uuid of app in the configure file have not changed after I deleted the older one and created the new one.
I have tried to delete the slave app "cakebldr" and reload the app with "rhc app reload -a cake", but the issue still exists.
This issue also exists on fork_ami_opensource_console_77.
Raise severity to medium to get some attention, think this need to be fixed..
dan and paul looking at today
Fixed, waiting on pull request to merge before closing issue: https://github.com/openshift/crankcase/pull/473
(In reply to comment #5) > Fixed, waiting on pull request to merge before closing issue: > > https://github.com/openshift/crankcase/pull/473 Above code is merged in devenv_2157, move it to ON_QA.
Tested this issue on devenv_2158, it have been verified since the deleted case will not exist in the Jenkins server. SO i will put it verified.
(In reply to comment #7) > Tested this issue on devenv_2158, it have been verified since the deleted > case will not exist in the Jenkins server. SO i will put it verified. Sorry to make a mistake in the comments, I mean that the jenkins job on jenkin server will be deleted when user deleted the related application on devenv_2158. So user can build jenkins successful using the same name with the application already deleted.
I didn't update the status because the pull request was still outstanding when I left for the day, but it seems like QE already tracked it down and tested it. Many thanks for the rapid turnaround!