Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Cannot spin up AWS JIRA Software DC for app certification - No export named ATL-BastionPrivIp found.

William Crighton [CCC]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 19, 2023

I am having trouble spinning up an AWS Development AND Enterprise level deployment using either the CloudFormation instructions or the newer Terraform deployment instructions. Whenever I request to use a Bastion host I receive the following error and the deployment rolls back:

No export named ATL-BastionPrivIp found. Rollback requested by user.

I select 8.20.22 for the JIRA Software version

I am following the instructions on either of the following pages:

CloudFormation: Data Center App Performance Toolkit User Guide For Jira (CloudFormation deployment)

Terraform: Data Center App Performance Toolkit User Guide For Jira

Any help appreciated. I am going to post this to the Atlassian community as well to see if I can figure out what I’m going wrong.

Thanks

2 answers

1 accepted

0 votes
Answer accepted
William Crighton [CCC]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 20, 2023

I did not ever determine what was wrong with how I was trying to use the CloudFormation instructions. 

I did, however, determine (with Atlassian's assistance) what was wrong with my attempt at using the Terraform instructions, and that was I simply wasn't following them correctly. There is a part where you need to edit the dcapt-small.tfvars file and correctly comment/uncomment lines related to what JIRA version you were using. In my case I uncommented correctly the 'shared home' line but failed to uncomment the correct 'database' line. 

0 votes
William Crighton [CCC]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 19, 2023

I haven't actually managed to follow the Terraform instructions correctly, I'm still working on getting that done

William Crighton [CCC]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 19, 2023

Nope! The Terraform instructions are failing as well now:

 

module.jira[0].helm_release.jira: Still creating... [19m40s elapsed]
module.jira[0].helm_release.jira: Still creating... [19m50s elapsed]
module.jira[0].helm_release.jira: Still creating... [20m0s elapsed]

Warning: Helm release "jira" was created but has a failed status. Use the `helm` command to investigate the error, correct it, then run Terraform again.

with module.jira[0].helm_release.jira,
on modules/products/jira/helm.tf line 3, in resource "helm_release" "jira":
3: resource "helm_release" "jira" {


Error: context deadline exceeded

with module.jira[0].helm_release.jira,
on modules/products/jira/helm.tf line 3, in resource "helm_release" "jira":
3: resource "helm_release" "jira" {

Releasing state lock. This may take a few moments...

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
TAGS
AUG Leaders

Atlassian Community Events