-
Bug
-
Resolution: Fixed
-
Medium
-
5.9.4
-
None
-
Severity 2 - Major
-
Steps to reproduce
- Create a Stash linked repository in Bamboo
- Create a plan using the Stash repo
- Create a plan branch
- Delete key in Stash user profile
- Go to linked repository and resave the configuration to regenerate the keys
- 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
- is related to
-
-
- Closed
-
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page"){kind=icon}
- was cloned as
-
BDEV-10344 Loading...
[BAM-16446] Branch Plan SSH keys for Stash linked repositories are not updated when the keys are regenerated
Yes, that is indeed the case. If it is a bug, what is the recommended way to get around it?
Problem is fixed in 5.14 for any created plan branch. There's also an upgrade task that attempts to clean up the keys in existing repositories/branches but there's a chance some data won't be fixed (if the repository on branch differs too much from master we are not able to tell if it's intended or not). In that case you can go to branch source repository edit and switch "server overrides" part of the configuration off. (this is new feature in Bamboo 5.14)
DanaC
added a comment - This is in version 5.12.3.x DanaC
added a comment - My understanding from a long running support issue i have is that Bamboo still uses ssh keys at the user or system level depending on the permissions of the user invoking or creating Linked repository.. If they had full admin, then it created at system level, otherwise it still created at user level..
When i first learned of the new system level ssh creation from bamboo i was very excited that it would remove the 20000+ errors i get almost every 2 days because of user level ssh keys ( had bitbucket being down for backups, but thats a separate issue), and a different developer checking the build, (re)saving the report because they see a big red warning box. But no, it wasn't replacement, it was in addition to.
DanaC
added a comment - My understanding from a long running support issue i have is that Bamboo still uses ssh keys at the user or system level depending on the permissions of the user invoking or creating Linked repository.. If they had full admin, then it created at system level, otherwise it still created at user level..
When i first learned of the new system level ssh creation from bamboo i was very excited that it would remove the 20000+ errors i get almost every 2 days because of user level ssh keys ( had bitbucket being down for backups, but thats a separate issue), and a different developer checking the build, (re)saving the report because they see a big red warning box. But no, it wasn't replacement, it was in addition to. Hey @dlee is this still an issue now that BAM-14986 has been completed. Keys should no longer be attached to the user profile...
issue resolved