If you have an existing Data Center cluster and update its license, it does not update the shared home license value in its version of confluence.cfg.xml. This will cause a conflict when deploying new nodes using CloudFormation templates, even though they would normally retrieve the license from the database instead.
- Create a Data Center cluster with any valid license
- Change the license to a different, still valid one
- Deploy a new AWS node with CloudFormation template (using Quick Start AWS template as a base)
- Startup the node
- Newly built and deployed node will obtain license from database and join the cluster
- Newly built and deployed node will obtain license from database but fail to startup and join cluster, as the license changed in step 2 does not update in shared home confluence.cfg.xml
You can manually update the license in the shared home confluence.cfg.xml file in order to resolve the issue, however there is no current method to automatically update the key value in that file at this time