packer 1.0.2 VNC port failure

132 views
Skip to first unread message

Dan Tran

unread,
Jun 22, 2017, 8:00:06 PM6/22/17
to Packer

Hi

Upgrade from 1.0.0 to 1.0.2 fail on my VNC port

==> vmware-iso: Unable to find available VNC port between 5900 and 5964
2017/06/22 23:44:47 packer: 2017/06/22 23:44:47 Trying address: resx86.lss.com:5920...
2017/06/22 23:44:47 packer: 2017/06/22 23:44:47 Timeout connecting to: resx86.lss.com:5920 (check firewall rules)
2017/06/22 23:44:47 packer: 2017/06/22 23:44:47 Trying address: resx86.lss.com:5921...
2017/06/22 23:44:47 packer: 2017/06/22 23:44:47 Timeout connecting to: resx86.lss.com:5921 (check firewall rules)
2017/06/22 23:44:47 packer: 2017/06/22 23:44:47 Trying address: resx86.lss.com:5922...
2017/06/22 23:44:47 packer: 2017/06/22 23:44:47 Timeout connecting to: resx86.lss.com:5922 (check firewall rules)
2017/06/22 23:44:47 packer: 2017/06/22 23:44:47 Trying address: resx86.lss.com:5923...
2017/06/22 23:44:47 packer: 2017/06/22 23:44:47 Timeout connecting to: resx86.lss.com:5923 (check firewall rules)
2017/06/22 23:44:47 packer: 2017/06/22 23:44:47 Trying address: resx86.lss.5924...
2017/06/22 23:44:47 packer: 2017/06/22 23:44:47 Timeout connecting to: resx86.lss.com:5924 (check firewall rules)
2017/06/22 23:44:47 packer: 2017/06/22 23:44:47 Trying address: resx86.lss.com:5925...
2017/06/22 23:44:47 packer: 2017/06/22 23:44:47 Timeout connecting to: resx86.lss.com:5925 (check firewall rules)
2017/06/22 23:44:47 packer: 2017/06/22 23:44:47 Trying address: resx86.lss.com:5926...


suggestion is very much appreciated.  Downgrade back to 1.0.0 works

Thanks

-Dan


Matthew Hooker

unread,
Jun 22, 2017, 8:55:59 PM6/22/17
to Packer
Hi Dan,

We added a configurable timeout for discovering VNC ports. Sorry this broke in 1.0.2, don't know why that is yet. Would you try setting the env var `PACKER_ESXI_VNC_PROBE_TIMEOUT` to `30s` and tell me if it works?


--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/131c5c34-70c0-48a6-9761-26806788f2a2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Matthew Hooker

unread,
Jun 22, 2017, 8:58:54 PM6/22/17
to Packer
Think I figured out the issue. Pushing up a PR now

James Elmes

unread,
Jun 28, 2017, 6:50:59 PM6/28/17
to Packer
I have this same issue since moving to 1.0.2. Does anyone know a work around? mine fails with the vnc errors pretty much right away so i don't think its a timeout issue

==> Some builds didn't complete successfully and had errors:
--> Windows2012R2v3-2017-06: Unable to find available VNC port between 5900 and 6000

James

Alvaro Miranda Aguilera

unread,
Jun 28, 2017, 7:53:10 PM6/28/17
to packe...@googlegroups.com
hi

not sure is the same issue

can you share the template and run this in debug mode?



To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/3e4c5317-0bc6-452c-bbdd-1a402a815f96%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
Alvaro

James Elmes

unread,
Jun 28, 2017, 8:18:33 PM6/28/17
to Packer
Yes it was the same issue, i was setting environment variables wrong. I have been trying to set them in the windows system variables.. lol

this fixes it for me

$env:PACKER_ESXI_VNC_PROBE_TIMEOUT="30s"

cheers

 

Dan Tran

unread,
Jul 4, 2017, 5:26:49 PM7/4/17
to Packer

packer 1.0.3 is coming soon?

Thanks

-Dan

James Elmes

unread,
Jul 4, 2017, 6:28:24 PM7/4/17
to Packer
I sure hope so

Rickard von Essen

unread,
Jul 5, 2017, 1:39:12 AM7/5/17
to packe...@googlegroups.com
July 10, 2017 is the plan, see https://github.com/hashicorp/packer/milestone/23

(And it's great if you bild from master and verifies that your issues
are resolved. It's easy.)

On 5 July 2017 at 00:28, James Elmes <jamesro...@gmail.com> wrote:
> I sure hope so
>
> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in violation
> of those guidelines may result in your removal from this mailing list.
>
> GitHub Issues: https://github.com/mitchellh/packer/issues
> IRC: #packer-tool on Freenode
> ---
> You received this message because you are subscribed to the Google Groups
> "Packer" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to packer-tool...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/packer-tool/83a77e1e-70e5-4dc6-8af1-b2f97aec5765%40googlegroups.com.

Matthew Hooker

unread,
Jul 5, 2017, 4:12:00 PM7/5/17
to packe...@googlegroups.com
Just to reiterate, the workaround for this is to set `PACKER_ESXI_VNC_PROBE_TIMEOUT=30s`. Sorry for the hassle, but we'll wait until the next release to fix this.

James Elmes

unread,
Jul 6, 2017, 12:04:39 AM7/6/17
to Packer
This new version also takes a lot longer to kick off, sits there for about 20 seconds before starting.
Reply all
Reply to author
Forward
0 new messages