From 92cb6ae1d3137330c1ceb0ca0252e39a4fb75efc Mon Sep 17 00:00:00 2001 From: Moises Rodriguez Date: Fri, 9 Jul 2021 16:51:09 -0500 Subject: [PATCH 1/4] Update troubleshooting rack delete error Document case when deleting rack from console and the rack does not show anymore in the console, but resources are still in the AWS account. --- docs/help/troubleshooting.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/help/troubleshooting.md b/docs/help/troubleshooting.md index ee8df6c7..25bcf82b 100644 --- a/docs/help/troubleshooting.md +++ b/docs/help/troubleshooting.md @@ -20,6 +20,12 @@ When you know there is an issue and want to stop a deployment, you can run the ` As ALB routing rules must have a unique priority, Convox will generate a random one for each service in the range 1-50000 (the range allowed by AWS). This is generated from a checksum of the app name, service name, domain name, and a couple of other tweaks. It is very unlikely, but it is possible to have a collision between two separate services on the same rack. To solve this, simply slightly amend your app or service name to generate a different checksum. +## I get an error when deleting rack from Convox Console + +### I get `ERROR: ValidationError: Stack with id rack-name does not exist` + +When deleting a Rack from the Convox Console under certain circumstances the rack is removed from the Console, but the AWS resources are still in AWS. To remove resources you need to go to your AWS account console, then head over to CloudFormation in the same region you rack was created. Under stack there will be stacks with: `rack-name`, `rack-name-app-name`, `rack-name-console-xxx`. Select them and then click Delete from the CloudFormation options. This will remove all the resources created for you rack. + ## My app deployed but I cannot access it Run `convox services` to find the load balancer endpoints for your application. From 6419730de80044891c3a32d4bc9e820731f9e2e5 Mon Sep 17 00:00:00 2001 From: Moises Rodriguez Date: Wed, 21 Jul 2021 11:00:57 -0500 Subject: [PATCH 2/4] Add Cloudwatch note --- docs/help/troubleshooting.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/help/troubleshooting.md b/docs/help/troubleshooting.md index 25bcf82b..36072baf 100644 --- a/docs/help/troubleshooting.md +++ b/docs/help/troubleshooting.md @@ -26,6 +26,8 @@ As ALB routing rules must have a unique priority, Convox will generate a random When deleting a Rack from the Convox Console under certain circumstances the rack is removed from the Console, but the AWS resources are still in AWS. To remove resources you need to go to your AWS account console, then head over to CloudFormation in the same region you rack was created. Under stack there will be stacks with: `rack-name`, `rack-name-app-name`, `rack-name-console-xxx`. Select them and then click Delete from the CloudFormation options. This will remove all the resources created for you rack. +Note: Some resouces as Cloudwatch logs might still exists after this process. + ## My app deployed but I cannot access it Run `convox services` to find the load balancer endpoints for your application. From 005a825c28f8c7a789758013168c1d10189f3edc Mon Sep 17 00:00:00 2001 From: Brian Galura Date: Fri, 27 Aug 2021 10:28:58 -0700 Subject: [PATCH 3/4] Update troubleshooting.md --- docs/help/troubleshooting.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/help/troubleshooting.md b/docs/help/troubleshooting.md index 36072baf..80163725 100644 --- a/docs/help/troubleshooting.md +++ b/docs/help/troubleshooting.md @@ -24,9 +24,9 @@ As ALB routing rules must have a unique priority, Convox will generate a random ### I get `ERROR: ValidationError: Stack with id rack-name does not exist` -When deleting a Rack from the Convox Console under certain circumstances the rack is removed from the Console, but the AWS resources are still in AWS. To remove resources you need to go to your AWS account console, then head over to CloudFormation in the same region you rack was created. Under stack there will be stacks with: `rack-name`, `rack-name-app-name`, `rack-name-console-xxx`. Select them and then click Delete from the CloudFormation options. This will remove all the resources created for you rack. +When deleting a Rack from the Convox Console under certain circumstances the rack is removed from the Console, but the AWS resources are still in AWS. To remove resources you need to go to your AWS account console, then head over to CloudFormation in the same region your rack was created. Under stack there will be stacks with: `rack-name`, `rack-name-app-name`, `rack-name-console-xxx`. Select them and then click Delete from the CloudFormation options. This will remove all the resources created for your rack. -Note: Some resouces as Cloudwatch logs might still exists after this process. +Note: Some resources as Cloudwatch logs might still exists after this process. ## My app deployed but I cannot access it From c248203e536029525c3db3364642d0bd11890f8e Mon Sep 17 00:00:00 2001 From: Brian Galura Date: Fri, 27 Aug 2021 10:30:33 -0700 Subject: [PATCH 4/4] Update troubleshooting.md --- docs/help/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/help/troubleshooting.md b/docs/help/troubleshooting.md index 80163725..236bf740 100644 --- a/docs/help/troubleshooting.md +++ b/docs/help/troubleshooting.md @@ -26,7 +26,7 @@ As ALB routing rules must have a unique priority, Convox will generate a random When deleting a Rack from the Convox Console under certain circumstances the rack is removed from the Console, but the AWS resources are still in AWS. To remove resources you need to go to your AWS account console, then head over to CloudFormation in the same region your rack was created. Under stack there will be stacks with: `rack-name`, `rack-name-app-name`, `rack-name-console-xxx`. Select them and then click Delete from the CloudFormation options. This will remove all the resources created for your rack. -Note: Some resources as Cloudwatch logs might still exists after this process. +Note: Some resources as Cloudwatch logs might still exist after this process. ## My app deployed but I cannot access it