You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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
locked and limited conversation to collaborators
Mar 31, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
crashwontfixOut of scope/alignment with the project, or issue is expected, intended behavior
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.
The text was updated successfully, but these errors were encountered: