Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-72297

Upgrading a plugin makes CDN cache unusable and has to be manually invalidated

      Issue Summary

      whenever there are plugin-related changes (like updating the plugin, enabling/disabling the plugin, install a new plugin) we see that the CDN cache is broken, and hence the page layout displayed on Jira UI is all distorted and broken.

      After invalidating the cache on the CDN front, things are working fine again.

      Steps to Reproduce

      N/A

      Expected Results

      We don't refer to the old CDN cache. A new cache should be referred and the old one should be manually invalidated.

      Actual Results

      page layout displayed on Jira UI is all distorted and broken.
      No exceptions in the logs.

      Workaround

      Manually invalidating the cache on the CDN front resolves the problem.

            [JRASERVER-72297] Upgrading a plugin makes CDN cache unusable and has to be manually invalidated

            Paul FLYE SAINTE MARIE added a comment - - edited

            +1 : affect our team and very anoying !
            Still affecting the version 9.12.12.

            Paul FLYE SAINTE MARIE added a comment - - edited +1 : affect our team and very anoying ! Still affecting the version 9.12.12.

            Nicu added a comment - - edited

            +1
            This also shows up in 8.22, I would not consider this a Low priority because it is quite annoying to always have to invalidate whenever we update apps and we had to put up a process in place around updating apps  to factor in the batch.css/js invalidation as well now.
            This can become even more cumbersome if the invalidation is slow, especially on global distributions, we usually end up with at least some locations still being served an old version of the file.

            This behavior makes it very difficult to install any app updates without affecting at least some locations in our set-up.

            Nicu added a comment - - edited +1 This also shows up in 8.22, I would not consider this a Low priority because it is quite annoying to always have to invalidate whenever we update apps and we had to put up a process in place around updating apps  to factor in the batch.css/js invalidation as well now. This can become even more cumbersome if the invalidation is slow, especially on global distributions, we usually end up with at least some locations still being served an old version of the file. This behavior makes it very difficult to install any app updates without affecting at least some locations in our set-up.

            Aditya M added a comment -

            What do we know so far?

            The contentVersionID before the plugin upgrade and the contentVersionID after the plugin upgrade is mixed up with few CSS files and hence the CDN has wrong CSS cached and has to be manually invalidated.

            Aditya M added a comment - What do we know so far? The contentVersionID before the plugin upgrade and the contentVersionID after the plugin upgrade is mixed up with few CSS files and hence the CDN has wrong CSS cached and has to be manually invalidated.

              Unassigned Unassigned
              amukkamala Aditya M
              Affected customers:
              16 This affects my team
              Watchers:
              22 Start watching this issue

                Created:
                Updated: