Welcome to cookiecutter-openedx-devops Discussions!

[lpm0073]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[Soporte-Crezee]

Hi Mr. Lawrence !

I'm follow the tutorial, i already finish the cookiecutter cuestionarie, but when I get to this part:

git remote add origin https://github.com/lpm0073/openedx_devops.git

git push -u origin main

I can't do the push, I wrote my git user and my token but the following appears:

remote: Permission to lpm0073/openedx_devops.git denied to Soporte-Crezee.
fatal: unable to access 'https://github.com/lpm0073/openedx_devops.git/': The requested URL returned error: 403

[Soporte-Crezee]

Hello again !

I am at step "III. Build Your Open edX Backend" and when I run "terragrunt apply" on the path "./terraform/environments/{{ cookiecutter.environment_name }}/vpc", the command starts correctly but after Terraform has been initialized successfully, I get the following error:

Error: no matching Route53Zone found
│
│ with data.aws_route53_zone.environment_domain,
│ on route53.tf line 16, in data "aws_route53_zone" "environment_domain":
│ 16: data "aws_route53_zone" "environment_domain" {
│
╵
ERRO[0018] 1 error occurred:
* exit status 1

[lpm0073]

you should manually add an AWS Route53 hosted zone for your project's environment domain. If for example, you want host the LMS at the domain courses.myschool.edu, then note that the root domain is myschool.edu whereas the environment domain is courses.myschool.edu is the environment domain. The Terraform module expects the environment domain to already exist in your AWS Route53 hosted zones.

[Soporte-Crezee]

Hello again! and excuse me for my constant posts.

I am in step III "Build Your Open edX Backend ", when I execute the command "terragrunt run-all apply" in the corresponding folder, I get 3 errors, 2 are messages that indicate the following: "Error: Error acquiring the state lock" and the last message indicates: "Error: no matching EC2 Key Pair found".

I don't understand how to solve these problems, for the "state lock" messages I have tried the commands "terraform force-unlock " and "terraform force-unlock -force " but neither works. Regarding the third message, I honestly have no idea how to fix it.

Attached the images of these errors and I thank you for the great support you have given me.

Additionally, i have these messages:

[lpm0073]

this is great feedback, thank you!! :D Please note the following:

1. "Error: Error acquiring the state lock". This is a Terraform error indicating that it either cannot access the AWS S3 bucket in which the state of your AWS account is persisted, or that the content of the DynamoDB table that is automatically created by Terraform is corrupted. The first step you should attempt is to delete the DynamoDB table (there will be one table per environment). Terraform will automatically replace the table and its contents during its "init" process. If that does not fix the problem then you should review the corresponding AWS S3 bucket, the name of which begins with a 12-digit number, like this, "320713933456-terraform-tfstate". Terraform creates this bucket for you automatically. If you see the bucket then just empty its contents. Terraform will automatically rebuild the database.
2. "Error: no matching EC2 Key Pair found". You see this error because you chose the Cookiecutter option to create an EC2 bastion, but you have not yet created an SSH key pair for the instance. You have to manually create the key pair from the EC2 console, and then afterwards you provide the name of the key as a Cookiecutter parameter.

[Soporte-Crezee]

Hi Mr. Lawrence! good Monday

I'm still on step 3, I tried to run the "terragrunt apply" command on the eks_clb_ec2 folder but I got the following error:
╷
│ Error: Unsupported argument
│
│ on main.tf line 26, in provider "kubernetes":
│ 26: load_config_file = false
│
│ An argument named "load_config_file" is not expected here.
╵
ERRO[0016] 1 error occurred:
* exit status 1

Do you have any idea what could be happening?
I add an image

[lpm0073]

Confirming that I was able to duplicate your error above. Summarizing the steps to resolve:

• completely delete the repository that you created with the Cookiecutter
• re-create your repository from Cookiecutter using latest
• re-run the Terragrunt scripts

more detail: you've somehow gotten an older set of Terraform code (from around 2 months ago) running against a new installation of AWS EKS Elastic Kubernetes Service. The specific error you posted above is a line from the old source code, referencing a boolean flag, "load_config_file" that has since been deprecated.

[lpm0073]

it's good that you're reporting these hurdles. i'm sure others will have similar if not identical experiences. this forum is searchable on Google, which should help the community.

[Soporte-Crezee]

Hello Mr. Larence!

Thank you very much for your great help.

I did what you recommended, I deleted the repository with the old code and created a new one with the current code.

Everything goes very well, until I get to step 3 "III. Build Your Open edX Backend"

I am now applying the terragrunt commands on each element following the specified order, now I am in the "kubernetes_ingress_clb" folder and run terragrunt init, validate, plan with no problems, however when I run terragrunt apply it stays at "helm_release.nginx: Still creating..." and at the end it gives me a timed out error.

do you have any idea about the reason of the error message?

I add images.

terragrunt int

terragrunt validate

terragrunt plan

terragrunt apply

terragrunt apply error message

[lpm0073]

Hello, confirming that the same thing happened to me yesterday. Re-running the apply operation a second time worked fine. It appears that I should extend the timeout period a few more minutes.

[Soporte-Crezee]

Hi Mr. Lawrence, I hope you are having a good week.

I tell you that I followed your suggestion, after the "timed out" message appeared i ran the "terragrunt apply" command a second time, but it didn't work, however i ran the apply command several times and got the same message error.

Could it be that the problem is in the time limit (5 minutes)?

In that case, How or in which file i change the time limit?

If the above is no the case, What could be happening?

*Update:

I put a time of 30 minutes, but in minute 21 it gave me the following error:

╷
│ Error: Kubernetes cluster unreachable: the server has asked for the client to provide credentials
│
│ with helm_release.nginx,
│ on main.tf line 50, in resource "helm_release" "nginx":
│ 50: resource "helm_release" "nginx" {
│
╵

I add image