-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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
Sporadic issues installing Ubuntu packages after apt-get update on AWS #29
Comments
This comment was originally opened by @catsby as hashicorp/terraform#2995 (comment). It was migrated here as part of the provider split. The original comment is below. Hey @llevar – are you able to run the same provisioniong scripts outside of Terraform with no issue? This appears to be an error situation outside of Terraform itself, e.g. Terraform is running the scripts, but they themselves are not completing successfully. Looking at your See our docs here: Try adding this to your security group resource: egress {
from_port = 0
to_port = 0
protocol = "-1"
cidr_blocks = ["0.0.0.0/0"]
} |
This comment was originally opened by @llevar as hashicorp/terraform#2995 (comment). It was migrated here as part of the provider split. The original comment is below. Hi @catsby. Thanks for your response. I tried running the commands manually and they do succeed. I also tried running the shell scripts that Terraform generates and they also succeed. Of course my sample is small. I've done many more terraform apply's than manual script runs. When it comes to egress rules, my deployment is not into a VPC and egress rules are not supported in EC2 Classic. The default all enabled Egress rule is applied instead, so that shouldn't be an issue. |
This comment was originally opened by @clstokes as hashicorp/terraform#2995 (comment). It was migrated here as part of the provider split. The original comment is below. @llevar the provisioning issue you're having may be due to some timing issues between cloud-init completing and Terraform running it's provisioners. hashicorp/packer#2639 and hashicorp/packer#41 (comment) provide some more context and workarounds that may be worth trying. |
I install salt multiple time using masterless provisioner and also with the package from disto repo - without any problems. |
I have the same issue aws_instance.bastion (remote-exec): Reading state information... Done
aws_instance.bastion (remote-exec): E: Unable to locate package python-minimal
Error: error executing "/tmp/terraform_354182919.sh": Process exited with status 100
terraform --version 130 ↵
Terraform v0.12.20
+ provider.aws v2.49.0
+ provider.null v2.1.2 |
avoids apt install failure issues related with this problem: hashicorp/terraform-provider-aws#29
Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label. If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
This issue was originally opened by @llevar as hashicorp/terraform#2995. It was migrated here as part of the provider split. The original body of the issue is below.
I'm trying to install Saltstack packages using apt-get and am getting very inconsistent behaviour. About 60% of my provisioning runs fail complaining about not being able to find the salt packages. Others finish with no problems. This is deploying to AWS US-East with a Ubuntu 14.04 AMI.
My .tf file:
https://gist.github.com/llevar/b9a2bd8823d8bd0f2993
A typical error looks like this:
The text was updated successfully, but these errors were encountered: