fork/exec /opt/packer_1.5.1: permission denied

[Runkar]

Hey,

i ran into this error with the newest version of packer (v1.5.1):

Failed to initialize build 'vsphere-iso': error initializing builder 'vsphere-iso': fork/exec /opt/packer_1.5.1: permission denied

==> Builds finished but no artifacts were created.

I checked all file- and user-permissions on both the host and the vCenter. With the previous v1.4.5 of packer everything works fine. Can you confirm this?

RHEL 7.7 Packer v1.5.1 vsphere-builder 2.3

[cattywampus]

I'm seeing the same error on my Mac (Catalina 10.15.2). Using Packer 1.5.1 (installed via home-brew) with vsphere-iso gives me that error:

Failed to initialize build 'vsphere-iso': error initializing builder 'vsphere-iso': fork/exec /usr/local/bin: permission denied

==> Builds finished but no artifacts were created.

Rolling back to 1.4.5 worked for me. Thanks for the workaround tip.

[amikkelsendk]

I see the same error on v.1.5.1 on CentOS.

On 14.01.2020 13:17, Jens Schütz wrote:

Hey,

i ran into this error with the newest version of packer (v1.5.1):

Failed to initialize build 'vsphere-iso': error initializing builder 'vsphere-iso': fork/exec /opt/packer_1.5.1: permission denied

==> Builds finished but no artifacts were created.

I checked all file- and user-permissions on both the host and the vCenter. With the previous v1.4.5 of packer everything works fine. Can you confirm this?

RHEL 7.7 Packer v1.5.1 vsphere-builder 2.3

-- You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub [1], or unsubscribe [2].

Links:

[1] https://github.com/jetbrains-infra/packer-builder-vsphere/issues/300?email_source=notifications&email_token=AILSAWTZIMHBEWWQMILMYFDQ5WUMXA5CNFSM4KGSBMX2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IGBE7NQ [2] https://github.com/notifications/unsubscribe-auth/AILSAWSPB7TLVMVB6ZI227DQ5WUMXANCNFSM4KGSBMXQ

[smithhannahm]

Looks like there were some backwards incompatibilities introduced in packer v1.5.0, specifically:

core: Changes have been made to both the Prepare() method signature on the builder interface and on the Provision() method signature on the provisioner interface. [GH-7866]

[bhundven]

https://github.com/jetbrains-infra/packer-builder-vsphere/issues/294

vsphere-iso is in the upcoming 1.5.2 packer release, you should download the pre-release and test.

[bhundven]

Sorry, I meant the nightly release:

https://github.com/hashicorp/packer/releases

[Runkar]

294

vsphere-iso is in the upcoming 1.5.2 packer release, you should download the pre-release and test.

That is great news!! Didn't expect that to happen after my previous conversation with Hashicorp. So I guess with the release of packer v1.5.2 this issue is outdated. I will close it after the official release.

[ccoager]

vsphere-clone is also broke but I don't see any mention of that in the 1.5.2 release. Any idea when this will be addressed?

[smithhannahm]

@ccoager Both vsphere-clone and vsphere-iso are in the new 1.5.2 release, though the changelog doesn't make that particularly clear. I've tested some of our vsphere-clone templates with the nightly build, and they worked without modification.

[zyra83]

Same thing here with packer 1.5.1.

[bhundven]

@zyra83 see: https://github.com/jetbrains-infra/packer-builder-vsphere/issues/300#issuecomment-577390975

[Runkar]

After the official hashicorp release this issue is outdated. Thank you!