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

Branch Plan SSH keys for Stash linked repositories are not updated when the keys are regenerated

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • 5.14.0
    • 5.9.4
    • None

      Steps to reproduce

      1. Create a Stash linked repository in Bamboo
      2. Create a plan using the Stash repo
      3. Create a plan branch
      4. Delete key in Stash user profile
      5. Go to linked repository and resave the configuration to regenerate the keys
      6. Check the SSH keys used by the master branch and the branch via the database

      Expected Behaviour

      The branch plan repositories should use the same keys as the master plan

      Observed Behaviour

      The branch plan keys are still using the outdated keys

        1. repo_override.png
          repo_override.png
          161 kB

            [BAM-16446] Branch Plan SSH keys for Stash linked repositories are not updated when the keys are regenerated

            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Bamboo Workflow 2016 v1 - Restricted [ 1443440 ] New: JAC Bug Workflow v3 [ 3385648 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Symptom Severity Original: Major [ 14431 ] New: Severity 2 - Major [ 15831 ]
            Bob Sewell (Inactive) made changes -
            Labels Original: ccr repository_refactoring New: repository_refactoring
            Bob Sewell (Inactive) made changes -
            Labels Original: repository_refactoring New: ccr repository_refactoring

            Cherry added a comment -

            issue resolved

            Cherry added a comment - issue resolved

            danieljk17 added a comment -

            Yes, that is indeed the case.  If it is a bug, what is the recommended way to get around it?  

            danieljk17 added a comment - Yes, that is indeed the case.  If it is a bug, what is the recommended way to get around it?  
            ThiagoBomfim (Inactive) made changes -
            Link New: This issue is related to BAM-17982 [ BAM-17982 ]
            Marcin Gardias made changes -
            Remote Link New: This issue links to "Page (Extranet)" [ 220386 ]
            Marcin Gardias made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Needs Triage [ 10030 ] New: Resolved [ 5 ]
            Marcin Gardias made changes -
            Status Original: Open [ 1 ] New: Needs Triage [ 10030 ]

              mgardias Marcin Gardias
              dlee@atlassian.com Deric Lee (Inactive)
              Affected customers:
              5 This affects my team
              Watchers:
              17 Start watching this issue

                Created:
                Updated:
                Resolved: