Issue Summary

Bitbucket Data Center upgrade guide document states : 

5. Copy Bitbucket to remaining nodes

The next step is to replicate your upgraded Bitbucket directories to other nodes in the cluster.  

1. Stop Bitbucket on the first node.

1. Copy the installation directory and local home directory from the first node to the next node. 
   If the path to the local home directory is different on this node, edit the /bin/set-bitbucket-home.sh to point to the correct location. 

1. Start Bitbucket and confirm that everything works as expected.

1. Stop Bitbucket on this node before continuing with the next node. 

It is misleading to suggest copying the installation directory from one node to another. This is not considered a best practice. In fact, it is strongly advised against copying the local home directory between nodes, as the local home is specific to each node.

Steps to Reproduce

Bitbucket Data Center upgrade guide document provides incorrect recommendations. 

Expected Results

The recommendation is to download the installer or the zip/tar file on each node and then configure the new installation to point to the existing local home directory. 

Actual Results

The current documentation states:

5. Copy Bitbucket to remaining nodes

The next step is to replicate your upgraded Bitbucket directories to other nodes in the cluster.  

1. Stop Bitbucket on the first node.

1. Copy the installation directory and local home directory from the first node to the next node. 
   If the path to the local home directory is different on this node, edit the /bin/set-bitbucket-home.sh to point to the correct location. 

1. Start Bitbucket and confirm that everything works as expected.

1. Stop Bitbucket on this node before continuing with the next node. 

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available