Problems running packer against deployments with a large number of hosts

[ddelnano]

Problems running packer against deployments with a large number of hosts

[ebrainte]

@ddelnano finally, the issue was having too many hosts, hehe ;D

Ive found the issue. The module tries to create a TCP conn to the master host, instead of doing it directly to the host where the created vm is. That's why when you tried, it worked (probably because your VM booted on the master host).

I ran packer until the instance booted on the master host, and it worked, thats why i figured that out.

I will create a PR with the fix, but i want to keep testing more

[ebrainte]

Ive created a PR for this issue:
#15

[fabiorauber]

Just tested with Packer 1.6.5: same result.

[ddelnano]

@fabiorauber sorry for responding late on this. I'm not sure why but I missed all the recent notifications for this repo.

I appreciate the detailed bug report and I'll need to spend some time looking into this error.

[ebrainte]

Im getting exacly the same error.

@ddelnano i saw that you tested the last release on your local env. Are you using xenserver or xcp-ng on your hosts?

[ddelnano]

I'm using xenserver but I believe I have tested this against XCP-ng albeit it was not the most recent testing. Let me give that a try today and see if I can reproduce your issue.

[ddelnano]

I just tested this against a XCP-ng 8.2.0 host and the VNC connection worked fine

==> xenserver-iso: Step: Create Instance
==> xenserver-iso: Using the following SR for the VM: OpaqueRef:fee129f3-e01c-47b5-be9c-6ec836b6bfe9
==> xenserver-iso: Created instance '3ad8e6c2-0bf9-6986-524e-c578c53ff8ae'
==> xenserver-iso: Step: Start VM Paused
==> xenserver-iso: Step: Set SSH address to VM host IP
==> xenserver-iso: Set host SSH address to '172.16.210.11'.
==> xenserver-iso: Unpausing VM 3ad8e6c2-0bf9-6986-524e-c578c53ff8ae
==> xenserver-iso: Waiting 10s for boot...
==> xenserver-iso: Connecting to the VM console VNC over xapi
==> xenserver-iso: Making HTTP request to initiate VNC connection: CONNECT /console?uuid=51c6c07f-622c-53f9-2649-b4b582db51a6 HTTP/1.0
==> xenserver-iso: Cookie: session_id=OpaqueRef:c5e70e94-ba57-4e2a-947c-e614c1ea98a2
==> xenserver-iso:
==> xenserver-iso:
==> xenserver-iso: Received response: HTTP/1.1 200 OK
==> xenserver-iso: Connection: keep-alive
==> xenserver-iso: Cache-Control: no-cache, no-store
==> xenserver-iso:
==> xenserver-iso:

@ebrainte @fabiorauber can you confirm that the "console" tab in the Xen orchestra UI works? As in the view you can see in my second screenshot.

The packer builder is connecting to the Xen console in the same fashion as that so I would expect them to both fail if that was the case.

@ebrainte what version of XCP-ng are you using?

[ebrainte]

Yes, vnc console works fine on XOA. What i didnt try, is with a pool with only 1 server (my pool has 18 servers on it).

Im using the XCP-ng 8.1.0.

Ive checked the XOA Source Code, and as you said, the method to connect is pretty much the same, but they add the header "Host" on the connection:
https://github.com/vatesfr/xen-orchestra/blob/master/packages/xo-server/src/proxy-console.js
line 34

Ive tried to add it on this module and the same is happening. I dont know what else to try

[ddelnano]

@ebrainte I would be surprised if the size of the pool mattered. While my Xenserver test environment is a single host, the XCP-ng deployment I used is a pool with 3 nodes.

[fabiorauber]

That explains a lot @ebrainte. The XCP-ng 7.6 Pool that was used for my tests has 11 servers, and the 8.0 one has 14. The odds of the machine starting on the Pool master in this situation are quite small.

@ddelnano, my XenOrchestra console works fine as well. I will try to run XCP-ng in a VM on my laptop, to compare the results.

[4censord]

You guys did just fix my problem i didn't know understand i had...
Everything was working on my dev system with 1 host, but everything was failing on some bigger pools

[ddelnano]

haha I stand corrected and now in hindsight it makes alot of sense 😄

[ddelnano]

Thanks to @ebrainte, the fix will be released in v0.3.1!