Clustered Confluence Data Center's new installation ends up with shared home artefacts being created at the node's local home instead

Issue Summary

When Confluence Data Center is installed and then setup as a clustered deployment, artefacts that are supposed to be created/placed at the instance's shared home directory get placed at the local home instead.

In Confluence 7.13.x

• the analytics-logs directory is created at local home (instead of shared home)
• the attachments directory is created at both local as well as shared home
• actual attachments get placed in the attachments directory at shared home

In Confluence 7.14.x onwards

• the analytics-logs directory is created at local home (instead of shared home)
• the attachments directory is created only at local home (instead of shared home)
• actual attachments get placed in the attachments directory at local home (instead of shared home)

Reproducible on Data Center: yes

Steps to Reproduce

1. Download Confluence's installer zip file (7.13.0, 7.14.0, or 7.19.1)
2. Unzip the file, create and specify the appropriate local home directory, database etc.
3. Start Confluence, enter the setup phase, and choose Clustered installation. Specify values for:
   • Cluster name
   • Shared home directory (note this value)
   • Network interface
   • Join configuration
4. Complete the installation, create a page, attach a file to the page.

Expected Results

Artefacts such as the attachments, analytics-logs should be created at the shared home directory

Actual Results

Artefacts such as the attachments, analytics-logs get created at the local home directory instead.

Workaround

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