Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-5483

Updating Crowd DC license doesn't reflect on the other nodes

      When using Crowd Datacenter, changing the license on one node will not refresh on the other nodes automatically even after waiting several hours.

      The license is updated correctly on the shared_home/crowd.cfg.xml file.

      Expected behavior

      Refreshing the licence page on each node should indicate the updated license in the UI.

      Proposed changes

      Crowd nodes should read the license from the shared crowd.cfg.xml file when the license page UI is reloaded.

      Workaround

      1) Restart the other nodes after updating the license on one node.
      2) Update the license on each node manually.

            [CWD-5483] Updating Crowd DC license doesn't reflect on the other nodes

            Tom Kielty added a comment - - edited

            This still applies to 5.1.3.

            Can the workaround be updated to show either or? As we can log into each node and apply the license.

            Tom Kielty added a comment - - edited This still applies to 5.1.3. Can the workaround be updated to show either or? As we can log into each node and apply the license.

            Thanks to @Rodrigo Girrardi for posting the issue in the first place. In the case of our customer, this issue also occurred and the version is 4.4.0. Please add it to the affected version. It is not a critical issue, but I hope it will be fixed because it is a part that causes inconvenience when customers extend or upgrade their licenses.

            Commercial Account Polaris Office added a comment - Thanks to @Rodrigo Girrardi for posting the issue in the first place. In the case of our customer, this issue also occurred and the version is 4.4.0. Please add it to the affected version. It is not a critical issue, but I hope it will be fixed because it is a part that causes inconvenience when customers extend or upgrade their licenses.

            I suggest that Atlassian create a KB article on the workaround for this issue while this issue is still open and is yet to be worked.

            Narendra Joshi added a comment - I suggest that Atlassian create a KB article on the workaround for this issue while this issue is still open and is yet to be worked.

              8df7baf53f92 aanastasov
              rgadami Rodrigo Girardi Adami
              Affected customers:
              9 This affects my team
              Watchers:
              19 Start watching this issue

                Created:
                Updated:
                Resolved: