Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Done
-
prod/bigpicture/jiracloud/2020/12/02/21_40
-
prod/bigpicture/jiracloud/2020/12/08/12_00, prod/biggantt/jiracloud/2020/12/08/12_00, prod/bigtemplate/jiracloud/2020/12/16/15_10, prod/biggantt/jiracloud/2021/06/18/22/20, prod/bigtemplate/jiracloud/2021/06/18/22/20, prod/bigpicture/jiracloud/2021/06/18/22/20, prod/biggantt/jiraserver/2021/07/13/18/00/8.1.0, prod/bigpicture/jiraserver/2021/07/13/18/00/8.1.0, prod/bigpictureenterprise/jiraserver/2021/07/13/18/00/8.1.0, prod/bigtemplate/jiraserver/2021/07/13/18/00/8.1.0
-
None
-
No
-
-
Infrastructure
-
BigPicture, BigPicture Enterprise, BigGantt, BigTemplate
-
JIRA cloud, Trello, One cloud
-
-
Sprint 2020/26
-
PI2020/5
-
2 minutes, 31 seconds -
4 hours, 13 minutes, 43 seconds -
7 minutes, 2 seconds -
16 minutes, 11 seconds -
13 hours, 30 minutes, 13 seconds -
1 minute, 9 seconds -
3 days, 13 minutes, 24 seconds -
Description
Tenant set as DORMANT will not properly activate on next client request. Due to this bug system installation with database snapshot can be activated only by SystemInstallationMovementJob.
In this case it could be activated by using CloudManager MBEAN (TenantLifecycleMBean).