Open cvedia-mdsol opened 10 months ago
Hi @cvedia-mdsol,
Thanks for reaching us, we are looking at your issue Best regards,
@outscale-toa is there a particular version of the plugin I can attempt to use as an alternative? I've tried a few of the recent ones by just changing the 'ssh_interface' to "private_ip" but it times out. Ran test to confirm that during initial creation I can connect fine to the public but not the private IP. We have the SSH port allowed in the referenced Security Group.
Hello @cvedia-mdsol,
We are presently trying to reproduise this issue, we did not manage to reproduce the bug yet.
In the meantime, could you please try to increase ssh_timeout, ex: ssh_timeout: "25m"
source "outscale-bsusurrogate" "linux" {
...
ssh_interface = "private_ip"
ssh_username = "outscale"
communicator = "ssh"
ssh_timeout = "15m"
ssh_private_key_file = "~/.ssh/outscale-infrastructure.rsa"
ssh_keypair_name = "outscale-infrastructure"
}
build {
sources = [
"source.outscale-bsusurrogate.linux"
]
}
Thanks
Overview of the Issue
Packer is able to connect fine via SSH when using our loaded key in Outscale however, this stopped working when switching the 'ssh_interface' to "private". We are using the 'outscale-bsusurrogate' builder for this.
Reproduction Steps
1.) Use the 'outscale-bsusurrogate' and outscale plugin '1.1.3' 2.) Add in SSH configuration using the following added parameters (this should connect fine)
3.) Switch the 'ssh_interface' with all other parameters the same (this should fail to connect and timeout)
Plugin and Packer version
Simplified Packer Buildfile
For the build, extracted the SSH parameters and provided them below. Was able to confirm that by only switch the 'ssh_interface', packer was no longer able to connect via SSH.
-Working Config-
-Not Working Config-
Operating system and Environment details
Executing Packer on Windows Server 2019 hosted in Outscale.
Log Fragments and crash.log files