Open kashifest opened 1 year ago
Hi @kashifest this looks to be an issue with OpenStack, which may have already been fixed in the in the latest release of the plugin. Looking at the provided build logs I believe you are using the version of OpenStack that is bundled with Packer in 1.8.6, which may be old. Please upgrade your version of the OpenStack plugin and try again.
You can upgrade by using the Packer plugins install command packer plugins install github.com/hashicorp/openstack
or if you are using HCL2 templates you can add the required plugins block to your template file and run packer init
to install the required plugin.
packer {
required_plugins {
openstack = {
version = ">= 1.1.0"
source = "github.com/hashicorp/openstack"
}
}
}
I'm going to move this issue to the OpenStack Plugin repo as this is not an issue with Packer core.
Please feel free to close the issue if you find that ssh is working without having to set the key pair type after upgrading.
Please feel free to close the issue if you find that ssh is working without having to set the key pair type after upgrading.
Thanks I will check and get back, we build a docker image with packer as one of the base images and use that with an image builder template json file. Is there anyway to specify the openstack plugin version in the template without needing to packer init ?
I previously reported a similar bug here hashicorp/packer#11656 but since I couldn't comment there , I am opening up a new issue here.
Packer version: 1.8.6 Tested with: CentOS Stream 9 and Ubuntu 22.04
Error:
Error waiting for SSH: Packer experienced an authentication error when trying to connect via SSH. This can happen if your username/password are wrong. You may want to double-check your credentials as part of your debugging process. original error: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
Packer log:
Workaround: Adding the following in builder template works:
"temporary_key_pair_type": "ed25519"