Summary

If, by mistake or intentionally, a white space is present at the beginning of a release name, then Bamboo won't be able to deploy the release returning the error:
"Deployment release with version xxxxxx cannot be found"

Environment

5.12.0-D20160518T090318

Steps to Reproduce

1. In Bamboo open a deployment project
2. Click on the Deploy button on the upper right corner of the page and select an environment where to deploy
3. In the next screen, select Create new release from build result
4. Enter the release name, start the deployment and see that everything works fine the first time
5. Repeat steps 1 to 3 but this time select "Promote existing release to this environment" and select the release you just created.

Expected Results

No error message is returned and the release is correctly deployd

Actual Results

The error message "Deployment release with version xxxxxx cannot be found" is displayed

The below error message is in the logs:

@40000000574fe8bf143f960c 2016-06-02 10:05:09,338 WARN [ajp-nio-127.0.0.105-8009-exec-41] [TextProviderHelper] The first TextProvider in the ValueStack (com.atlassian.bamboo.deployments.versions.actions.ViewDeploymentVersion) could not locate the message resource with key 'Release:  bingel-2.0.3-beta-16 / cms-1.13.10'
@40000000574fe8bf1448a65c 2016-06-02 10:05:09,340 WARN [ajp-nio-127.0.0.105-8009-exec-41] [TextProviderHelper] The default value expression 'Release:  bingel-2.0.3-beta-16 / cms-1.13.10' was evaluated and did not match a property.  The literal value 'Release:  bingel-2.0.3-beta-16 / cms-1.13.10' will be used.

Notes

• This happens because the white space at the beginning of the release name is stripped away from the url called when deploying and this returns an error because the release name in Bamboo DB still has the white space at the beginning

Workaround

Remove the leading white space from the release name in Bamboo DB.