Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ec2_public_dns not found #19

Open
keenanandrew opened this issue Nov 10, 2023 · 0 comments
Open

ec2_public_dns not found #19

keenanandrew opened this issue Nov 10, 2023 · 0 comments

Comments

@keenanandrew
Copy link

Hi there, thanks for this excellent tutorial!

I'm getting stuck at the 'make cloud-airflow' command. Everything up until then has run correctly.

However I get the following error after running make cloud-airflow:

terraform -chdir=./terraform output -raw private_key > private_key.pem && chmod 600 private_key.pem && ssh -o "IdentitiesOnly yes" -i private_key.pem ubuntu@$(terraform -chdir=./terraform output -raw ec2_public_dns) -N -f -L 8081:$(terraform -chdir=./terraform output -raw ec2_public_dns):8080 && open http://localhost:8081 && rm private_key.pem
╷
│ Error: Output "ec2_public_dns" not found
│
│ The output variable requested could not be found in the state file. If you recently added this to your configuration,
│ be sure to run `terraform apply`, since the state won't be updated with new output variables until that command is
│ run.
╵
╷
│ Error: Output "ec2_public_dns" not found
│
│ The output variable requested could not be found in the state file. If you recently added this to your configuration,
│ be sure to run `terraform apply`, since the state won't be updated with new output variables until that command is
│ run.
╵
ssh: Could not resolve hostname : Name or service not known
make: *** [Makefile:72: cloud-airflow] Error 255

I've checked the Terraform statefile, it's completely blank. Not sure if that's normal.

Running terraform apply gives the following:

╷
│ Error: No configuration files
│
│ Apply requires configuration to be present. Applying without a configuration would mark everything for destruction,
│ which is normally not what is desired. If you would like to destroy everything, run 'terraform destroy' instead.

Please advise! Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant