-
Notifications
You must be signed in to change notification settings - Fork 38
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
Upgrade builder to latest packer version #5
Conversation
The example is almost working. It seems there is a problem ssh'ing to the instance after it has booted and ran kickstart properly
|
After debugging this more, I've tracked this down to the provisioner step. If I uncomment it, the packer builder runs fine and the ubuntu and centos examples work as expected. Since that was working prior to this change, that will need to be fixed before this can be merged. |
Hi, im still getting this error when using your binary release for linux with packer 1.6.5. Do i need to compile it from source? Failed to initialize build 'xenserver-iso': error initializing builder 'xenserver-iso': Incompatible API version with plugin. Plugin version: 4, Ours: 5 |
@fanuelsen the builder does not support packer above v0.10.2 until I'm able to merge this PR and build new binaries. You could try this branch out yourself but please be aware that there are still bugs to fix and it is not ready for use. I will hopefully be addressing the remaining issues over the next week. |
Thanks for pointing me in the right direction. I guess winrm is broken at this time? [ERROR] connection error: unknown error Post http://127.0.0.1:5900/wsman: read tcp 127.0.0.1:45978->127.0.0.1:5900: read: connection reset by peer. |
@fanuelsen all of my focus has been on linux so far (the examples that exist in master). I have created #6 to track fixing the winrm issue. Can you please add the packer file and your reproduction steps for that error? I will look into that separately from building packer from the latest version. I'm not familiar with winrm at all so whatever additional context you can provide would be greatly appreciated. |
After enabling packer logging (through the
|
The ssh agent error (which I was investigating before I noticed the type assertion issue) ended up not being an issue. Once the type assertion issue was fixed, I had a successful build even with |
This PR upgrades the builder's packer dependency to v1.6.5. This is the most recent release of packer until the packer plugin sdk was introduced (in v1.6.6).
Additional testing
keep_vm
is set appropriately)SSH_AUTH_SOCK
causes failures now that the type assertion issues are fixed - logs an error but does not fail the build