Packer: PACKER_HTTP_ADDR is not available for use by the PowerShell provider

[erikgraa]

Overview of the Issue

PACKER_HTTP_ADDR environment variable is not available for use by the PowerShell provider.

The only three variables I could enumerate that start with packer (using gci env: and piping it to a file to look at post-deploy) are these:

Reproduction Steps

Create a machine with vsphere-iso using the http_directory, and http_min_port and http_max_port. The port is set to 9000 for both directives, and http_directory points to a "http" folder.

I have tried both "inline" and "scripts" options for the provider.

Packer version

1.5.5

Simplified Packer Buildfile

Operating system and Environment details

Windows Server 2019 Standard

[nywilken]

Hi @erikgraa thanks for reaching out. The issue is actually with the vsphere-iso builder as it is not properly setting the PACKER_HTTP_ADDR variable. I'm able to reproduce this issue using the shell provisioner. I don't know if we will be able to make this fix immediately but will see if we can get to it by the 1.5.7 release if not sooner.

[erikgraa]

Thank you for clarifying. I will continue to send in the Packer host's IP by other means until such time as vsphere-iso makes available PACKER_HTTP_ADDR to providers. :)

[razaborg]

I seem to have the exact same issue with the vmware-iso provisionner.

[erikgraa]

I seem to have the exact same issue with the vmware-iso provisionner.

I circumvent it until fixed by sending in the packer host's IP as an environment variable.

[sylviamoss]

hello there! Could you please test your templates with these binaries https://circleci.com/gh/hashicorp/packer/52124#artifacts/containers/0 ?
This changes the way we save HTTP information and I wonder if it would solve the issue.

[SwampDragons]

Related to https://github.com/hashicorp/packer/pull/9238

[SwampDragons]

The PR linked above solves this issue, and it will be part of the v1.6.0 release. Let us know if you find any more problems!

[hashibot[bot]]

I'm going to lock this issue because it has been closed for _30 days_ ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.