antisaWiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
{{tag>troubleshooting atlassian}}

====== Atlassian apps AWS testing troubleshooting ======

===== Error: timed out waiting for the condition =====

<code>
module.confluence[0].helm_release.confluence: Still modifying... [id=confluence, 34m58s elapsed]
module.confluence[0].helm_release.confluence: Still modifying... [id=confluence, 35m8s elapsed]
module.confluence[0].helm_release.confluence: Still modifying... [id=confluence, 35m18s elapsed]

Error: timed out waiting for the condition

  with module.confluence[0].helm_release.confluence,
  on modules/products/confluence/helm.tf line 4, in resource "helm_release" "confluence":
   4: resource "helm_release" "confluence" {
</code>

[[https://aws.amazon.com/premiumsupport/knowledge-center/ec2-on-demand-instance-vcpu-increase/|Raise]] [[https://us-east-2.console.aws.amazon.com/ec2/home?region=us-east-2#LimitsCalculator:|the limits]] for [[https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-on-demand-instances.html#vcpu-limits-request-increase|ec2]] instance

===== Error: context deadline exceeded =====
Full error:

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

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


Error: context deadline exceeded

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

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

</code>

The above happened while trying to deploy 4-node confluence cluster. Try these solutions:

  - Try rerunning install.sh but setting the ''confluence_replica_count'' back to 1 or 2, then deploy, then set replica count to 3, deploy and then do it for 4 replicas
  - Try removing the .kube config folder from your home directory
  - Make sure the max capacity is not low in "Autoscaling Group" in AWS console, maybe set it to 5 just in case

==== Tested on ====
  * 2023.06 Atlassian
  * Ubuntu 22.04
  * aws-cli/2.9.2 Python/3.9.11 Linux/5.19.0-46-generic exe/x86_64.ubuntu.22 prompt/off
  * helm version.BuildInfo{Version:"v3.10.2", GitCommit:"50f003e5ee8704ec937a756c646870227d7c8b58", GitTreeState:"clean", GoVersion:"go1.18.8"}
  * kubectl: Client Version: version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.4", GitCommit:"872a965c6c6526caa949f0c6ac028ef7aff3fb78", GitTreeState:"clean", BuildDate:"2022-11-09T13:36:36Z", GoVersion:"go1.19.3", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.7
Server Version: version.Info{Major:"1", Minor:"25+", GitVersion:"v1.25.11-eks-a5565ad", GitCommit:"df109513ba589adaee235b4e658476275d1fde31", GitTreeState:"clean", BuildDate:"2023-06-16T17:35:00Z", GoVersion:"go1.19.10", Compiler:"gc", Platform:"linux/amd64"}
  * 2.4.0 branch of https://github.com/atlassian-labs/data-center-terraform.git

====== See also ======
  * [[wiki:terraform_troubleshooting|terraform troubleshooting]]
====== References ======
  * https://atlassian-labs.github.io/data-center-terraform/troubleshooting/TROUBLESHOOTING/