Deployment Fails due to deletion of build from Inbox

OttoFMS
1

I’ve come across some unexpected behaviour in OttoFMS. I’m running Otto version 4.7.0 and FMS 21.0.2 on both servers involved.

I’m deploying multiple copies of a file set to a destination server but with different names.

On Server A there is a set of tiles that I wish to deploy to Server B multiple times
File 1, File 2, File 3

I created a build of the files from Server A and used the push build feature to push it to the inbox on Server B.
I then setup a deployment with source Destination build Inbox and destination Server B specifying the build in the Inbox as the Default Build.

I then setup multiple sub deployments such that
File 1 (Install/Replace) → File 1_A
File 2 (Install/Replace) → File 2_A
File 3 (Install/Replace) → File 3_A

File 1 (Install/Replace) → File 1_B
File 2 (Install/Replace) → File 2_B
File 3 (Install/Replace) → File 3_B

File 1 (Install/Replace) → File 1_C
File 2 (Install/Replace) → File 2_C
File 3 (Install/Replace) → File 3_C

etc

I then ran the deployment, the first sub deployment ran without issue, the subsequent sub deployments failed with

DeploymentError: BUILD_SOURCE_NOT_FOUND - Build not found in inbox: UNDERPIN

I expected the build would have persisted for the entirety of the deployment allowing it to be copied multiple times to the destination server.

2

Hi again…

That should definitely work. Files should not be removed from the inbox until all the sub deployments are done. We’ll look into this.

Thanks for reporting.

Todd

4

Thanks Todd, appreciate the quick response

5

Hey @jamesatdf ,

This issue is fixed with OttoFMS version 4.7.1! Let me know if you have any issues with it going forward.

-Kyle

1 Like