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

Packer crashing non-deterministically #6310

Closed
oguzhanunlu opened this issue May 25, 2018 · 3 comments
Closed

Packer crashing non-deterministically #6310

oguzhanunlu opened this issue May 25, 2018 · 3 comments
Labels
crash wontfix Out of scope/alignment with the project, or issue is expected, intended behavior

Comments

@oguzhanunlu
Copy link

Packer version: 0.12.3

Crash report is here

Today, I published first release candidate of a project successfully however publishing second release candidate failed where only change was a variable representing project version in Packerfile.

Thanks in advance.

@SwampDragons
Copy link
Contributor

There's a very, very good chance that we've fixed this crash in the time since 0.12.3 came out. I know I've done work on the ami region copy step that's failing here. Try with a more recent version of Packer and let me know if it's still an issue. You may want to run Packer fix yourconfig.json to check for any backwards incompatibilities that have popped up since you upgraded.

@SwampDragons SwampDragons added wontfix Out of scope/alignment with the project, or issue is expected, intended behavior crash labels May 25, 2018
@oguzhanunlu
Copy link
Author

Thanks a lot @SwampDragons , bumping to 1.2.3 followed by using packer fix solved my problem.

@ghost
Copy link

ghost commented Mar 31, 2020

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.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Mar 31, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
crash wontfix Out of scope/alignment with the project, or issue is expected, intended behavior
Projects
None yet
Development

No branches or pull requests

2 participants