Details
-
Bug
-
Resolution: Fixed
-
Low
-
5.15.3, 5.14.5
-
None
-
Severity 2 - Major
-
Description
Summary
When modifying the 'bamboo.config.directory' property in bamboo.cfg.xml, Bamboo doesn't look for the cipher file in this updated location.
Environment
- Bamboo 5.15.3
Steps to Reproduce
- Install Bamboo 5.15.3
- Set up a linked repository with authentication that authenticates via keys, passwords, or passphrases.
- Stop Bamboo 5.15.3.
- Move the ${bambooHome}/xml-data/configuration directory to a new location.
- Update the 'bamboo.config.directory' property in bamboo.cfg.xml to point to this new location.
- Start up Bamboo 5.15.3
- Attempt to edit existing linked repositories.
Expected Results
- View and edit the existing linked repositories without issues.
Actual Results
No existing linked repositories are shown.
The below exception is thrown in the atlassian-bamboo.log file:
2017-03-21 23:22:17,714 ERROR [http-nio-8085-exec-5] [ExceptionMappingInterceptor] Unknown cipher data id 0 java.lang.IllegalArgumentException: Unknown cipher data id 0 at com.google.common.base.Preconditions.checkArgument(Preconditions.java:122)
Workaround
Don't move the cipher directory and 'cipher.key_0' file when updating the bamboo.config.directory.
Leave the configuration directory structure in place for the Bamboo home directory and keep the 'cipher.key_0' in place.