Unable to Upgrade Jira Data Center on AWS

[Harish.konala]

Hi Team,

We are using AWS Quick Start (https://confluence.atlassian.com/enterprise/running-jira-on-an-aws-cluster-969535550.html) to run our own Jira SM setup in AWS.

Now that we want to upgrade the Jira SM version to 4.22.1 from 4.13.4, cloudformation update stack is failing VPSStack as the Export from VPCStack is being used by another stack.

Embedded stack arn:aws:cloudformation:eu-west-2:*********:stack/atlassian-sandbox-jira-service-management-VPCStack-****/*********************** was not successfully updated. Currently in UPDATE_ROLLBACK_IN_PROGRESS with reason: Export JSM-SBX-BastionPrivIp cannot be updated as it is in use by atlassian-sandbox-jira-service-management-JiraDCStack-***********

I tried removing that direct export and used a workaround with parameters but no luck so far. I highly appreciate any help to unblock me here

Thanks in advance

Harish  

[Oleksandr Metelytsia]

Hello,

Please do scaling directly via the autoscaling group:

AWS console -> ec2 -> Auto scaling -> Auto scaling groups -> your stack ASG -> edit desired min and max capacity to the needed number.

[Chris Surman]

This is depressing seeing this coming from someone in the Atlassian team. You've probably snatched this info from:
 https://developer.atlassian.com.rproxy.goskope.com/platform/marketplace/dc-apps-performance-toolkit-user-guide-bitbucket/

However, that suggestion contradicts other documentation:
https://confluence.atlassian.com/enterprise/administering-jira-data-center-on-aws-969535552.html

It's not a working workaround if you need to make ANY changes to the stack. So we need to be able to make those changes in the stack without this error, especially for upgrades.

I have exactly the same problem with 1 out of 3 of our environments

Export ATL-Jira-DevBastionPrivIp cannot be updated as it is in use by Jira-Dev-JiraDCStack

It's a complete blocker, and a bug, yet nobody seems to be taking it seriously.

Look at the instructions for upgrading on the AWS Stacks: https://confluence.atlassian.com/adminjiraserver/upgrading-jira-data-center-on-aws-945105105.html#:~:text=In%20the%20AWS%20console%2C%20go,current%20template%20and%20click%20Next.

It leaves us dead in the water, this needs an urgent fix.

[Arthur]

It really is a shame that atlassian doesn't have a fix for this critical bug. It also occurs for confluence stacks.

[Anton Kronseder _smartics_]

Hi Harish,

i did run in the same Problem.

Any solution found?

Thanks,

Anton

[freatt]

Hi Harish,

Did you resolve this?

If so, how?

I just ran into a similar problem when performing the Atlassian Performance testing, where I need to scale up from 1 to 2 nodes in the data center cluster.

My error:

Embedded stack arn:aws:cloudformation:eu-central-1:948378585301:stack/Jira-DM-PerfTest-Enterprice-2022-T1-VPCStack-1P8O7SLFYNF4I/c07c2e90-f070-11ec-a074-06c427dcdb5c was not successfully updated. Currently in UPDATE_ROLLBACK_IN_PROGRESS with reason: Export ATL-BastionPrivIp cannot be updated as it is in use by Jira-DM-PerfTest-Enterprice-2022-T1-JiraDCStack-D439FRHDRKPJ

Thanks,

Fredrik