-
Suggestion
-
Resolution: Unresolved
-
None
Problem Definition
The current path with Zero Downtime Upgrade (ZDU) when both Jira Software and Jira Service Management (JSM) are installed on the same instance is to manually copy files from the JSM .obr to the proper location of the shared-home.
Manual operations on the file system can be error prone, which could impact the upgrade flow.
Suggested Solution
It would be great to have a way to rely on all ZDU features without being required to manually copying files from the .obr.
For example, we could rely on upgrading JSM through the versions and licenses page by clicking on the update button.
That would make the necessary files available, without removing the old .jar files before the administrator triggers the upgrade tasks.
The below steps are a suggestion and not an actual upgrade path, since following it currently will delete old JSM .jar files, making the ZDU rollback unfeasible for JSM.
- Put Jira on upgrade mode.
- Upgrade all nodes to the target version.
- Upgrade JSM to the target version by clicking on the upgrade button on the versions and licenses page.
- Finalize the ZDU upgrade.
- links to
[JSDSERVER-8658] As a Jira administrator I would like to upgrade Jira Service Management with the push of a button when relying on ZDU with Jira Software installed
| Labels | Original: affects-zdu | New: affects-zdu ril |
| Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 977871 ] |
| Description |
Original:
h3. Problem Definition
The current path with [Zero Downtime Upgrade|https://confluence.atlassian.com/adminjiraserver/upgrading-jira-data-center-with-zero-downtime-938846953.html] (ZDU) when both Jira Software and Jira Service Management (JSM) are installed on the same instance is to manually copy files from the JSM {{.obr}} to the proper location of the {{shared-home}}. Manual operations on the file system can be error prone, which could impact the upgrade flow. h3. Suggested Solution It would be great to have a way to rely on all ZDU features without being required to manually copying files from the {{.obr}}. For example, we could rely on upgrading JSM through the _versions and licenses_ page by clicking on the _update_ button. That would make the necessary files available, without removing the old {{.jar}} files before the administrator triggers the upgrade tasks. The below steps are a suggestion and not an actual upgrade path, since following it currently will delete old JSM {{.jar}} files, making the ZDU rollback unfeasible for JSM. # Put Jira on upgrade mode. # Upgrade all nodes to the target version. # Upgrade JSM to the target version by clicking on the _upgrade_ button on the _versions and licenses_ page. # Finalize the ZDU upgrade. |
New:
h3. Problem Definition
The current path with [Zero Downtime Upgrade|https://confluence.atlassian.com/adminjiraserver/upgrading-jira-data-center-with-zero-downtime-938846953.html] (ZDU) when both Jira Software and Jira Service Management (JSM) are installed on the same instance is to manually copy files from the JSM {{.obr}} to the proper location of the {{shared-home}}. !screenshot-1.png|thumbnail! Manual operations on the file system can be error prone, which could impact the upgrade flow. h3. Suggested Solution It would be great to have a way to rely on all ZDU features without being required to manually copying files from the {{.obr}}. For example, we could rely on upgrading JSM through the _versions and licenses_ page by clicking on the _update_ button. That would make the necessary files available, without removing the old {{.jar}} files before the administrator triggers the upgrade tasks. The below steps are a suggestion and not an actual upgrade path, since following it currently will delete old JSM {{.jar}} files, making the ZDU rollback unfeasible for JSM. # Put Jira on upgrade mode. # Upgrade all nodes to the target version. # Upgrade JSM to the target version by clicking on the _upgrade_ button on the _versions and licenses_ page. !screenshot-2.png|thumbnail! # Finalize the ZDU upgrade. |
| Attachment | New: screenshot-2.png [ 409445 ] |
| Attachment | New: screenshot-1.png [ 409444 ] |
| Labels | New: affects-zdu |