Jira Data Center AWS CloudFormation templates won't deploy additional nodes correctly if the database collation has been changed

Summary

Jira nodes created after the cluster has been deployed using the Atlassian-provided AWS CloudFormation templates will fail to install and run Jira if the database collation has been changed to a supported one.

Environment

• AWS CloudFormation deployment using the Atlassian-provided templates.

Steps to Reproduce

1. Deploy a Jira Data Center cluster in AWS following the instructions in https://aws.amazon.com/quickstart/architecture/jira/. The database will be created using the unsupported collation en_US.utf-8, as reported in JRASERVER-70077.
2. Change the database collation to C and table collation to DEFAULT by following the steps in the KB article Unsupported collation error thrown in Jira server using PostgreSQL.
3. Update the CloudFormation stack, increasing the parameters ClusterNodeMax and ClusterNodeMin, so a new node will be deployed.

Expected Results

The node is deployed correctly, Jira is installed and is able to run normally.

Actual Results

The EC2 instance will be launched, but Ansible automation will fail to install Jira, reporting the following errors:

TASK [database_init : Create application DB user] ******************************
changed: [localhost] => {"changed": true, "user": "atljira"}

TASK [database_init : Update root privs for new user] **************************
ok: [localhost] => {"changed": false}

TASK [database_init : Create application database] *****************************
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: NotSupportedError: Changing LC_COLLATE is not supported. Current LC_COLLATE: C
fatal: [localhost]: FAILED! => {"changed": fals

Workaround

None.