Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-60045

Updating license in Confluence Data Center does not allow new AWS Quick Deploy nodes to join cluster

      The fix for this bug has been released to our Long Term Support release.

      The fix for this bug is now available in the latest release of Confluence 7.13 and 7.19

      Issue Summary

      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.

      Steps to Reproduce

      1. Create a Data Center cluster with any valid license
      2. Change the license to a different, still valid one
      3. Deploy a new AWS node with CloudFormation template (using Quick Start AWS template as a base)
      4. Startup the node

      Expected Results

      • Newly built and deployed node will obtain license from database and join the cluster

      Actual Results

      • 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

      Workaround

      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

            [CONFSERVER-60045] Updating license in Confluence Data Center does not allow new AWS Quick Deploy nodes to join cluster

            A fix for this issue is available in Confluence Server and Data Center 7.20.0.
            Upgrade now or check out the Release Notes to see what other issues are resolved.

            James Whitehead added a comment - A fix for this issue is available in Confluence Server and Data Center 7.20.0. Upgrade now or check out the Release Notes to see what other issues are resolved.

            A fix for this issue is available in Confluence Server and Data Center 7.13.9.
            Upgrade now or check out the Release Notes to see what other issues are resolved.

            Saran Babu Pannuru (Inactive) added a comment - A fix for this issue is available in Confluence Server and Data Center 7.13.9. Upgrade now or check out the Release Notes to see what other issues are resolved.

            A fix for this issue is available in Confluence Server and Data Center 7.19.1.
            Upgrade now or check out the Release Notes to see what other issues are resolved.

            Madhubabu Kethineni (Inactive) added a comment - A fix for this issue is available in Confluence Server and Data Center 7.19.1. Upgrade now or check out the Release Notes to see what other issues are resolved.

            Still waiting.

            Karen Mixon added a comment - Still waiting.

            jj1978 added a comment - - edited

            I cannot fathom how this has not been remedied, this issue has been ongoing for ages. This is ridiculous particularly for those of us hosting on a Cloud environment where Auto Scaling practices etc are in use (as per Atlassians own Quickstart for AWS). The thing that's amusing is if license gets lost you even get a screen where the first person who logs in can potentially re-install the product and wipe the existing DB in doing so.

            jj1978 added a comment - - edited I cannot fathom how this has not been remedied, this issue has been ongoing for ages. This is ridiculous particularly for those of us hosting on a Cloud environment where Auto Scaling practices etc are in use (as per Atlassians own Quickstart for AWS). The thing that's amusing is if license gets lost you even get a screen where the first person who logs in can potentially re-install the product and wipe the existing DB in doing so.

            Is this in the backlog to fix? 

            Karen Mixon added a comment - Is this in the backlog to fix? 

            We have this issue in version 7.7.4 in onsite Data Center. it is a simple license change like we need every year.

            our environment does not a way to login to a specific node, therefore it is difficult to identity which nodes are still using the old key. Does anyone know if there is a way to identify which nodes are using the old key vs new?

            Sumanth Reddy added a comment - We have this issue in version 7.7.4 in onsite Data Center. it is a simple license change like we need every year. our environment does not a way to login to a specific node, therefore it is difficult to identity which nodes are still using the old key. Does anyone know if there is a way to identify which nodes are using the old key vs new?

            We encountered this issue when upgrading to Data Center from Server. This occurred on a upgrade from 7.5 to 8.13

            Adam Johnson added a comment - We encountered this issue when upgrading to Data Center from Server. This occurred on a upgrade from 7.5 to 8.13

            This sounds like an issue with Confluence then. I've updated the component to DC core.

            Steve Smith (Inactive) added a comment - This sounds like an issue with Confluence then. I've updated the component to DC core.

              a2879c3b3278 Jordan Anslow
              bcostales Bernabe Theodore Costales III
              Affected customers:
              23 This affects my team
              Watchers:
              42 Start watching this issue

                Created:
                Updated:
                Resolved: