Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-14927

Stash integration fails when Bamboo is upgraded from a pre-5.5 version

      Integrating two separate Bamboo instances with Stash 3.2.2 following the exact same process:
      1. A Bamboo 5.6.0 that I just upgraded from a 5.2.0 version
      2. A new installation of Bamboo 5.6.0

      If I create an application link to Stash in the first instance and a new Stash linked repository, build fails with:

      (com.atlassian.bamboo.repository.RepositoryException : java.lang.RuntimeException: com.atlassian.bamboo.plugins.stash.repository.StashRepositoryException: com.atlassian.bamboo.repository.RepositoryException: com.atlassian.bamboo.plugins.git.GitCommandException: command /usr/local/git/bin/git ls-remote ssh://2bc0fafd-3656-4c64-af3e-50b01ab98004@127.0.0.1:56880/tes/testgitrepo.git failed with code 128. Working directory was [.]., stderr: [Host key verification failed., fatal: Could not read from remote repository., , Please make sure you have the correct access rights, and the repository exists.])
      

      and it continuously shows the following in the terminal window from which I started Bamboo:

      The authenticity of host '[127.0.0.1]:56880 ([127.0.0.1]:56880)' can't be established.
      RSA key fingerprint is fc:1f:3c:61:5d:9a:28:b7:34:a5:93:3d:a0:12:2b:05.
      Are you sure you want to continue connecting (yes/no)? 
      The authenticity of host '[127.0.0.1]:56880 ([127.0.0.1]:56880)' can't be established.
      RSA key fingerprint is fc:1f:3c:61:5d:9a:28:b7:34:a5:93:3d:a0:12:2b:05.
      Are you sure you want to continue connecting (yes/no)? 
      The authenticity of host '[127.0.0.1]:56880 ([127.0.0.1]:56880)' can't be established.
      RSA key fingerprint is fc:1f:3c:61:5d:9a:28:b7:34:a5:93:3d:a0:12:2b:05.
      Are you sure you want to continue connecting (yes/no)? 
      The authenticity of host '[127.0.0.1]:56880 ([127.0.0.1]:56880)' can't be established.
      RSA key fingerprint is fc:1f:3c:61:5d:9a:28:b7:34:a5:93:3d:a0:12:2b:05.
      Are you sure you want to continue connecting (yes/no)? 
      The authenticity of host '[127.0.0.1]:56880 ([127.0.0.1]:56880)' can't be established.
      RSA key fingerprint is fc:1f:3c:61:5d:9a:28:b7:34:a5:93:3d:a0:12:2b:05.
      Are you sure you want to continue connecting (yes/no)? 
      The authenticity of host '[127.0.0.1]:56880 ([127.0.0.1]:56880)' can't be established.
      RSA key fingerprint is fc:1f:3c:61:5d:9a:28:b7:34:a5:93:3d:a0:12:2b:05.
      Are you sure you want to continue connecting (yes/no)? 
      The authenticity of host '[127.0.0.1]:56880 ([127.0.0.1]:56880)' can't be established.
      RSA key fingerprint is fc:1f:3c:61:5d:9a:28:b7:34:a5:93:3d:a0:12:2b:05.
      Are you sure you want to continue connecting (yes/no)? 
      

      Going through the exact same process for the second instance which is a new 5.6.0 installation, it works correctly and build succeeds with no issues.
      Does a Bamboo upgrade to a version after 5.5 follow the expected simplified workflow for Stash integration?

        1. From520AppLink.png
          From520AppLink.png
          117 kB
        2. From520FailedBuild.png
          From520FailedBuild.png
          236 kB
        3. From520LinkedRepo.png
          From520LinkedRepo.png
          196 kB
        4. From520Terminal.png
          From520Terminal.png
          167 kB
        5. New560GreenBuild.png
          New560GreenBuild.png
          418 kB
        6. New560Instance.png
          New560Instance.png
          124 kB
        7. New560Repo.png
          New560Repo.png
          220 kB

            [BAM-14927] Stash integration fails when Bamboo is upgraded from a pre-5.5 version

            There are no comments yet on this issue.

              Unassigned Unassigned
              ssetayeshfar Sepideh Setayeshfar (Inactive)
              Affected customers:
              3 This affects my team
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: