Build 'vsphere-iso' errored: error typing a boot command: ServerFaultCode: Cannot complete the operation due to an incorrect request to the server. #126
Comments
|
More info, please! What version of vSphere are you using? (6.0, 6.5, 6.7, etc). And, 2.0 was refactored to use packer > 1.2.0; I'm not sure if it requires that, but what happens if you try with a version of packer >= 1.2.0 ? |
|
Hi Eric,
I am using Packer version : 1.1.2 n our project got completed . We have
created images through manually
…On 17 July 2018 at 08:22, Eric ***@***.***> wrote:
More info, please! What version of vSphere are you using? (6.0, 6.5, 6.7,
etc).
And, 2.0 was refactored to use packer > 1.2.0; I'm not sure if it requires
that, but what happens if you try with a version of packer >= 1.2.0 ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#126 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ab1ad56t37GfDc7SdsgIvGIm65Db0H3eks5uHgFFgaJpZM4UspNb>
.
|
|
I have this issue with packer 1.2.4 and vsphere 6.5. Turns out the ESXi itself is running an older version so that's the issue |
|
Hello. Packer v 1.3.1 and vsphere v 6.5.0.20000. I got this error: |
|
Having the same problem. The weird thing is that sometimes it works, sometimes it doesn't. I've gone through the boot command manually step by step and it works. Packer 1.3.2 Boot command: Log: |
|
I hit the same issue when applying a Kickstart to centos. I think if it's not caused by the ESXi Host version then maybe it's a permissions thing... |
|
Packer version 1.3.1, packer-builder-vsphere version 2.0. Having the same issue now, and the builder doesn't report anything particularly useful. recently upgraded to vSphere 6.7, appears to be erroring consistently now. Working with our vSphere admin to logcrawl, check perms, etc, but it appears as though the upgrade might've broke something API-wise. |
|
Issue persists with Packer 1.3.3 and builder v2.1, and being granted full administrator access. So, it appears that something in the vSphere 6.7 API changed, and is breaking the builder (since I don't believe Packer handles vSphere communication directly). @mkuzmin does this have any relevance? vmware/govmomi@6478866 |
|
I don't have 6.7 yet, and never saw anything similar.
|
|
@mkuzmin I've hit this on VMware ESXi, 6.0.0, 6921384 Nothing in vCenter UI Event Windows. In Recent Tasks Window I just see this:
Enabled debugging packerlog.txt shows: Full log https://gist.github.com/dkirrane/73979e9f7fbf8a1e2e704f6455b15339 |
|
Same probleme here... Packer 1.3.5 and vCenter 6.5.0 |
|
Issue persists with packer v1.3.5, the jetbrains plugin v2.3 on macos, vSphere v6.7 It's as if the boot_command does nothing whatsoever. I've tried various permutations of the boot command all to no avail. Really want to get this working, but am completely dead in the water. log snippet: 2019/04/05 19:43:42 packer-builder-vsphere-iso.macos: 2019/04/05 19:43:42 Deleting floppy disk: /var/folders/48/j6191d8553j_61tkbqxk_68w0000gn/T/packer852014389 |
|
@gitcdb Same issue here. Did you get any solution:? |
|
@gowthamakanthan Unfortunately not, no. I had to resort to using the
standard vmware-iso package for now with the hopes that this is resolved at
some point.
…On Tue, 16 Apr 2019 at 03:15, gowthamakanthan ***@***.***> wrote:
@gitcdb <https://github.com/gitcdb> Same issue here. Did you get any
solution:?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#126 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AvC201VghJHdW_lO3g1dtnSZITgfgbeDks5vhaK8gaJpZM4UspNb>
.
|
|
@gitcdb I have overcome this by installing the latest plugin and packer. |
|
Still erroring on packer 1.4.0 and vsphere-iso 2.1. @dkirrane you need vSphere 6.5 and higher for boot_commands (and this builder) to work at all, I believe. @mkuzmin any updates or hope of progress on this? it's completely murdered our pipeline for months now; we're building images manually and that's flat out unscaleable. VMware logs don't provide any useful information that I can find. EDIT:
I no longer see the
Here's my boot_command for an ubuntu18.04 image: The Packer debug log doesn't show anything useful:
This issue persists with 2.0 and 2.1 and all versions of packer, as mentioned upthread.
yeah, as I mentioned above, I haven't found anything in the debug logs from either the raw ESXi host or the vCenter logs. |
|
@ideologysec Not sure why are you using the boot command like that. Please check the workable boot command below. {
"variables": {
"vsphere_uid": "{{env `vsphere_uid` }}",
"vsphere_passwd": "{{env `vsphere_passwd` }}",
"vsphere_vm_name": "null"
},
"builders": [
{
"type": "vsphere-iso",
"vcenter_server": "",
"username": "{{user `vsphere_uid` }}",
"password": "{{user `vsphere_passwd` }}",
"insecure_connection": "true",
"datacenter": "Platform-DC",
"cluster": "Platform-Cluster",
"datastore": "nfs_plat_101",
"network": "vlan23",
"vm_name": "{{user `vsphere_vm_name` }}",
"guest_os_type": "centos7_64Guest",
"ssh_username": "ansible",
"ssh_private_key_file": "/root/.ssh/ansible",
"ssh_bastion_host": "",
"ssh_bastion_username": "ansible",
"ssh_bastion_private_key_file": "/root/.ssh/ansible",
"CPUs": 1,
"RAM": 1024,
"RAM_reserve_all": false,
"convert_to_template": true,
"disk_controller_type": "pvscsi",
"disk_size": 61200,
"disk_thin_provisioned": true,
"network_card": "vmxnet3",
"iso_paths": [
"[ISO] linux/CentOS-7-x86_64-Minimal-1810.iso"
],
"iso_checksum": "13675c6f74880e7ff3481b91bdaf925ce81bda8f",
"iso_checksum_type": "sha1",
"floppy_files": [
"{{template_dir}}/ks.cfg"
],
"boot_command": "<esc> <wait> linux inst.text inst.ks=hd:fd0:/ks.cfg <enter>"
}
]
}And amusing Kickstart file as well. |
|
@gowthamakanthan Because Ubuntu Server starts with boot args there already; please check the examples in the repo or gaui's boot command upthread. It's a bit different than CentOS. :) My boot command has worked in previous versions, and works on other packer builders. Even using a CentOS.json with boot_command very similar to your own doesn't work, so I doubt very much that it's the formatting of the boot command. |
|
I've also run into this problem. Works in our labb environment running vSphere 6.7 Both use Packer 1.4.1 and vSphere-ISO 2.3 |
|
Same here. |
|
Was able to get this to work with this combination:
|
|
Works with packer 1.4.4 and vsphere-iso 2.3 against VMware ESXi, 6.5.0, 13932383 and vCenter 6.7. @ideologysec thank you for the vSphere version tip above. |
|
Not working with: |
|
I had this error: Tested with: Packer 1.3.4 I was missing the following permission in the Packer role: Inject USB HID scan codes Hopefully this helps someone. |
|
I found that my previous boot command leads to the USB HID pop-up on vCenter. This is a working builder: |
|
Sometimes, I get this error when Packer is typing in the boot_command: ==> Some builds didn't complete successfully and had errors: The error sometimes happens when Packer is typing in the boot_command. Usually, there are already some characters typed in successfully, i.e. the issue here is not a permission to input key presses. The VM remains running after the failure. Packer: 1.6.5 |
Same problem here, but only on pfsense template ? |
|
I'm seeing this intermittently (5-10% of my CI runs), using a Debian Buster packer host, running Packer v1.6.5 on Jenkins v2.249.2, interfacing with vSphere v6.7.0.44000, and a Debian Buster guests, with default settings in packer template for key and keygroup intervals, and the below boot_command. Incidentally, my Jenkins/Packer host is also running in the same vSphere cluster (with nested virtualization on, obviously), but from reading the other reports, this doesn't seem to be relevant. Are people having any success with setting longer key intervals? I'm loathe to do that bc the "typing boot command..." stage already takes a seemingly long time. I tend to think that my environment should have one of the lowest latency possible between the packer processes and the vSphere guest process, since it's all going through the internal networking of our vSphere data center (>=30Gbps). (BTW, I've played with several things to try to get the install console to be larger than the default, the above |
Hi Team,
We are using packer-builder-vsphere plugin with packer version 1.1.2
Here is our packer.json
{ "builders": [ { "type": "vsphere-iso", "vcenter_server": "XXX", "username": "XXX", "password": "XXX", "insecure_connection": "true", "vm_name": "rhel7-packer02", "cluster": "XXX", "host": "XXX", "datastore": "XXX", "guest_os_type": "rhel7_64Guest", "ssh_username": "packer", "ssh_password": "packer", "CPUs": 2, "RAM": 4096, "RAM_reserve_all": true, "disk_size": 32768, "network_card": "vmxnet3", "network": "XXX", "floppy_files":[ "ks.cfg" ], "boot_command": [ "<esc><wait>", "vmlinuz initrd=initrd.img net.ifnames=0 biosdevname=0 ", "ks=http://<IP>/kickstart/ks1.cfg", "<enter>" ], "iso_paths": [ "[XYXX] Linux-Iso/rhel-server-7.5-x86_64-boot.iso" ] } ], "provisioners": [ { "type": "shell", "inline": ["ls /"] } ] }I am facing an issue after running packer build
Packer build log
Any help is appreciated
The text was updated successfully, but these errors were encountered: