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
InvalidPermission.Duplicate when creating temporary AWS security group #878
Comments
Seeing this also. Randomly in different regions, at least one in 3 of my builders does it at the moment. 1392343473,,ui,say,amazon-instance_us-east-1 output will be in this color. |
I am experiencing the same thing. It happens intermittently, and is very frustrating when running multiple AWS builds at once. |
Apparently fixed via this? #552 |
I don't think so, @dmerrick. That was 4 months ago. I'm experiencing this problem with packer-0.5.1. |
Well, yes. As I said, I am experiencing it too. But apparently 4 months ago this issue was addressed. |
Made some changes upstream to the retry mechanisms of our AWS client that should hopefully fix this. In the next release, if it happens again, please let me know. |
Thanks, @mitchellh! |
I saw this today with packer-0.5.2. I'm running packer on OS X Mavericks. |
I just saw the same thing as phillipgoh:
|
I am seeing this in packer 0.6.0. Error launching source instance: The security group 'sg-32661e56' does not exist in VPC 'vpc-922db3f2' (InvalidGroup.NotFound) |
Just saw it again in Packer 0.6.0 myself. build 08-Jul-2014 02:30:20 1404786620,,ui,error,Build 'amazon_ebs_hvm_precise_us-east-1' errored: Error launching source instance: The security group 'sg-a5eb9cc0' does not exist (InvalidGroup.NotFound) |
Perhaps a variant: ==> amazon-ebs: Authorizing SSH access on the temporary security group... |
I got this on Packer 0.6.0 too. packer build packer_ami.json ==> amazon-ebs: Creating temporary keypair: packer 53c6aa4c-3d4f-c8b2-6d96-685021fc065c ==> Some builds didn't complete successfully and had errors: ==> Builds finished but no artifacts were created. |
Ditto for 0.6.0: ==> amazon-ebs: Creating temporary keypair: packer 53c8a7e8-8502-1398-a98a-9cfc4b894cf8 |
got this with 0.6.1
|
+1 getting this in 0.6.1 (using ubuntu 14.04) |
i also got this error in 0.6.1. I'm on OSX Mavericks.
|
I got this on 0.7.1 on amazon linux
|
I'm seeing this on Packer 0.7.5 running on OS X Yosemite. I was trying to create a new AMI based on AMI I had generated with packer just a few minutes before:
As with the other cases reported here, it doesn't happen all the time. |
I just got this error as well in Packer v0.7.5 on OS X Yosemite.
|
I just got this error with packer 0.8.3. I don't think this has been properly fixed :( EDIT: I actually think I got this error because amazon was having an outage. I think the error logging is just inaccurate. |
This is definitely still happening with packer 0.8.5 on Amazon Linux ==> amazon-ebs: Creating temporary security group for this instance...� |
@adimarco It looks to me like you have a different issue. Your error message is completely different. If you believe this is a bug, please open a new issue. |
@cbednarski Sorry, I meant to leave that comment in #1322. It was closed as a duplicate of this issue, however, and I see the same error message I'm getting in 2 other posts in this issue, so I thought might be related. I'll open a new issue. |
From @phinze
We should probably catch and ignore this issue since I think the system is in a state where it can continue in spite of the error. |
Just got this with 0.8.6:
|
Getting the following ==> amazon-ebs: Prevalidating AMI Name... |
Same issue as commented above, running packer version 0.10.1 on AWS Linux. UPDATE: Just executed the same build script and didn't receive the error on 3rd attempt. Successful after I attempted to use the -debug flag and then ran without it. |
According to some comments in #2606 this may happen when there is an API outage. Even if this is not the root cause these issues are likely related. |
Agreed, if I retry a minute or so later it runs with no errors. Thanks for the link to #2606! |
All - is this issue still ongoing? From the sounds of the conversations in May, it seems like this issue can be closed? |
@michaeltlombardi I'm still seeing the |
Are you using the current master of Packer? I don't think the fix from here #3656 has been cut into a release yet, 0.10.1 was cut before the fix and 0.10.2 was cut last week but doesn't look like it includes that fix. |
I'm using 0.10.2 now, from homebrew. Sent from my iPhone
|
@mwarkentin @ryanrupp 0.10.2 contains exactly the same code as 0.10.1 it was just rebuilt to support macOS Sierra. |
This happens for us both through the homebrew version and the compiled version from the Packer site. This is definitely still an issue. |
might be able to solve this with something like #3938 |
@laneatomic Can you confirm which error you're getting? Is it
|
was able to reproduce the I'm going to close this since I believe the |
Unfortunately I can no longer test this error. We refactored how we use Packer in a way to avoid this entirely. |
Have just come across this on 0.12.2
|
@jgillard Please open a new issue for this. Thanks! |
Using Packer 0.5.1, and the amazon-ebs builder, I'm seeing errors of the form:
It's not happening consistently, so may indicate a race-condition.
The text was updated successfully, but these errors were encountered: