[13:27] <eduardo71> Need a consultant to help us debug an issue with rack controllers in a cluster not syncing images
[14:56] <mup> Bug #1838943 opened: Cannot PXE boot arch 0f due to protocol mismatch <MAAS:Confirmed> <https://launchpad.net/bugs/1838943>
[15:43] <cyphermox> so; I have just installed MAAS in a VM, a very standard install on 18.04, I can login to the interface but it just remains at "Connecting..." forever after login
[15:43] <cyphermox> anyone has an idea what's wrong, what I can check?
[15:44] <cyphermox> rbasak: ^ pinging you, because I don't even know if this channel is the right place to be asking the question :)
[15:46] <rbasak> I think this channel is the right place
[15:46] <rbasak> But I don't know the answer, sorry.
[15:46] <rbasak> The MAAS team hang out here too I think though?
[15:48] <cyphermox> yeah I expected you might not know the answer
[15:48] <cyphermox> it's certainly different from all previous experiences
[15:48] <cyphermox> it's always worked before, but I've always deployed it on metal, now it's in a VMWare virtual machine
[16:52] <cyphermox> roaksoax: any idea ^
[20:05] <newell> cyphermox: ltrager might have an idea as I think he has messed with VMWare VMs, I personally have not and I have not seen what you are experiencing
[20:05] <cyphermox> well, even then whether it's hardware or a VM and which hypervisor should not matter at all
[20:05] <newell> cyphermox: I haven't seen what you are experiencing in general
[20:06] <cyphermox> yeah, I understand
[20:06] <newell> cyphermox: are you using main archive or ppa?
[20:06] <newell> or other?
[20:06] <ltrager> cyphermox: I've used MAAS to deploy VMware but I haven't deployed to VMware itself
[20:06] <cyphermox> ppa:maas/proposed
[20:06] <ltrager> I mean installed MAAS on VMware
[20:07] <newell> cyphermox: ppa:maas/2.7
[20:07] <newell> try that one if it is not too much trouble
[20:09] <ltrager> cyphermox: If you can't connect to the UI it could be there is a network rule blocking websockets
[20:09] <ltrager> cyphermox: To get around that try using an SSH sockets proxy
[20:11] <cyphermox> well, it's port 5240 isn't it?
[20:11] <cyphermox> or are there extra firewall rules required?
[20:15] <ltrager> cyphermox: 5240 is for the API, I believe 80 is still used for the websocket
[20:15] <ltrager> cyphermox: argh actually nevermind I was thinking of something else
[20:15] <ltrager> cyphermox: I have seen firewalls block just websockets while letting other traffic through
[20:18] <cyphermox> mmkay
[20:18] <cyphermox> I'm going to have to go beat things into submission