Regression : Re-indexing is triggered after Jira upgrade even after setting upgrade.reindex.allowed=false flag.

XMLWordPrintable

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Medium
    • 8.0.0
    • Affects Version/s: 7.3.0, 7.6.4, 7.6.9, 7.13.0
    • Component/s: Upgrade
    • 7.03
    • 4
    • Severity 3 - Minor
    • 1
    • Hide
      Atlassian Update – 21 December 2018

      Dear Jira users,

      We’re glad to announce that this issue will be addressed in our upcoming 8.0 release.

      You can find more details about our 8.0 beta release here — https://community.developer.atlassian.com/t/beta-for-jira-8-0-is-up-for-grabs/25588

      Looking forward to your feedback!

      Kind regards,
      Syed Masood
      Product Manager, Jira Server and Data Center

      Show
      Atlassian Update – 21 December 2018 Dear Jira users, We’re glad to announce that this issue will be addressed in our upcoming 8.0 release. You can find more details about our 8.0 beta release here — https://community.developer.atlassian.com/t/beta-for-jira-8-0-is-up-for-grabs/25588 Looking forward to your feedback! Kind regards, Syed Masood Product Manager, Jira Server and Data Center

      Test was performed with upgrading 6.3.15 to 7.6.4. After setting the flag upgrade.reindex.allowed=false and restarting the 6.3.15 version, upgrade to 7.6.4 was started. After successful upgrade the background re-indexing was started in spite of the flag being set. This seems to be a regression in 7.6.4 from the behaviour in 7.4.0 where it was fixed as per https://jira.atlassian.com/browse/JRASERVER-65568.

        1. atlassian-jira.log
          1.03 MB

            Assignee:
            Unassigned
            Reporter:
            shrivatsaa (Inactive)
            Votes:
            9 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated:
              Resolved: