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

builder/amazon: InvalidGroup.NotFound error #4368

Closed
mwhooker opened this issue Jan 5, 2017 · 5 comments · Fixed by #4369
Closed

builder/amazon: InvalidGroup.NotFound error #4368

mwhooker opened this issue Jan 5, 2017 · 5 comments · Fixed by #4369

Comments

@mwhooker
Copy link
Contributor

mwhooker commented Jan 5, 2017

2017/01/05 14:03:20 Waiting on builds to complete...
2017/01/05 14:03:20 Starting build run: amazon-instance
2017/01/05 14:03:20 Running builder: amazon-instance
2017/01/05 14:03:20 ui: ==> amazon-instance: Prevalidating AMI Name...
==> amazon-instance: Prevalidating AMI Name...
2017/01/05 14:03:22 packer: 2017/01/05 14:03:22 Using AMI Filters {
2017/01/05 14:03:22 packer:   ImageIds: ["ami-a8d369c0"]
2017/01/05 14:03:22 packer: }
2017/01/05 14:03:22 ui:     amazon-instance: Found Image ID: ami-a8d369c0
    amazon-instance: Found Image ID: ami-a8d369c0
2017/01/05 14:03:22 ui: ==> amazon-instance: Creating temporary keypair: packer_586ec2a8-a9ef-70ac-f6ab-3d123563edd4
==> amazon-instance: Creating temporary keypair: packer_586ec2a8-a9ef-70ac-f6ab-3d123563edd4
2017/01/05 14:03:22 ui: ==> amazon-instance: Creating temporary security group for this instance...
2017/01/05 14:03:23 packer: 2017/01/05 14:03:23 Temporary group name: packer 586ec2ab-314e-1e79-2a0b-b02fc242467e
==> amazon-instance: Creating temporary security group for this instance...
2017/01/05 14:03:23 ui: ==> amazon-instance: Authorizing access to port 22 the temporary security group...
==> amazon-instance: Authorizing access to port 22 the temporary security group...
2017/01/05 14:03:23 packer: 2017/01/05 14:03:23 [DEBUG] Waiting for tempSecurityGroup: sg-716d800d
2017/01/05 14:03:23 packer: 2017/01/05 14:03:23 [DEBUG] Timed out waiting for security group sg-716d800d
2017/01/05 14:03:23 ui: ==> amazon-instance: Deleting temporary security group...
==> amazon-instance: Deleting temporary security group...
2017/01/05 14:03:24 ui: ==> amazon-instance: Deleting temporary keypair...
==> amazon-instance: Deleting temporary keypair...
2017/01/05 14:03:24 ui error: Build 'amazon-instance' errored: Timed out waiting for security group sg-716d800d
2017/01/05 14:03:24 Builds completed. Waiting on interrupt barrier...
2017/01/05 14:03:24 machine readable: error-count []string{"1"}
2017/01/05 14:03:24 ui error:
==> Some builds didn't complete successfully and had errors:
2017/01/05 14:03:24 machine readable: amazon-instance,error []string{"Timed out waiting for security group sg-716d800d"}
2017/01/05 14:03:24 ui error: --> amazon-instance: Timed out waiting for security group sg-716d800d
2017/01/05 14:03:24 ui:
==> Builds finished but no artifacts were created.
2017/01/05 14:03:24 waiting for all plugin processes to complete...
Build 'amazon-instance' errored: Timed out waiting for security group sg-716d800d

==> Some builds didn't complete successfully and had errors:
--> amazon-instance: Timed out waiting for security group sg-716d800d

==> Builds finished but no artifacts were created.
2017/01/05 14:03:24 /Users/mwhooker/go/bin/packer: plugin process exited
2017/01/05 14:03:24 /Users/mwhooker/go/bin/packer: plugin process exited

unfortunately the original error gets lost. Made a change to print the error, and will report back once I find it.

@mwhooker
Copy link
Contributor Author

mwhooker commented Jan 5, 2017

hmm ok I think it's


2017/01/05 14:46:08 packer: 2017/01/05 14:46:08 [DEBUG] Timed out waiting for security group sg-1e719c62: Error looking for security group [0xc4204a8770]: InvalidGroup.NotFound: The security group 'sg-1e719c62' does not exist
2017/01/05 14:46:08 packer: 	status code: 400, request id: 34a9f059-671a-4326-8e87-b2ed9431ba1e

which was mentioned in #878

@mwhooker mwhooker changed the title timeout waiting for security group builder/amazon: InvalidGroup.NotFound error Jan 5, 2017
@bradydowling
Copy link

I got InvalidGroup.NotFound today on macOS Sierra with Packer. Simply retried the command and it ran fine the next time 👍

@mickengland
Copy link

mickengland commented Feb 13, 2017

I am getting this error and retrying doesn't work for me with version 0.12.2.

In my debug log I am seeing the group get created:

2017/02/13 10:46:08 packer: 2017/02/13 10:46:08 [DEBUG] Waiting for temporary security group: sg-a676f6b0
2017/02/13 10:46:08 packer: 2017/02/13 10:46:08 [DEBUG] Found security group sg-a676f6b0
2017/02/13 10:46:08 ui: ==> amazon-ebs: Launching a source AWS instance...
==> amazon-ebs: Launching a source AWS instance...
2017/02/13 10:46:09 ui error: ==> amazon-ebs: Error launching source instance: InvalidGroup.NotFound: The security group 'sg-a676f6b0' does not exist in VPC 'vpc-0ec6bb6a'
==> amazon-ebs: 	status code: 400, request id: bcb9d697-7ba3-4b56-b403-fbcc078d81d3
2017/02/13 10:46:09 ui: ==> amazon-ebs: No volumes to clean up, skipping
==> amazon-ebs: Error launching source instance: InvalidGroup.NotFound: The security group 'sg-a676f6b0' does not exist in VPC 'vpc-0ec6bb6a'

@rickard-von-essen
Copy link
Collaborator

@mickengland most likely a configuration error ask on the mailing list, provide your template and a packer log from running PACKER_LOG=1 packer build ....

@mickengland
Copy link

Thanks. Turned out I was missing the vpc_id.

@hashicorp hashicorp locked and limited conversation to collaborators Apr 4, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants