[03:50] <jianghuaw_> it looks like MAAS can't support VMs on XenServer: Enlistment failed due to cloud-init can find data source;
[03:51] <jianghuaw_> And with manually adding machines, it failed at commissioning.
[05:00] <ybaumy> jianghuaw_: i had that too with the datasource. it was a problem that it couldnt logon to the iscsi source. the reason for me was network problems. once they were solved it worked
[06:08] <jianghuaw_> ybaumy, that's useful input. I've not checked further. Will look into if it's the same issue. Thanks.
[06:24] <jianghuaw_> ybaumy, could you share more about the issue you met? It looks there is no way to login the failed VM.
[06:25] <ybaumy> jianghuaw_: somehow it was working when i installed another rack controller for that network i was trying to install the node in
[06:25] <jianghuaw_> But the cloud-config-url is really referred to the IP belong to another network.
[06:27] <jianghuaw_> e.g. the VM got IP from MAAS DHCP as 10.14.0.3; maas has two interfaces: eth0: 10.14.0.1; an the other is connected to public network.
[06:28] <jianghuaw_> From the VM's console, it has iscsi_target_ip=10.14.0.1 but the cloud-config-usl=http://<the MAAS' ip belong to the public network>.
[06:29] <jianghuaw_> Is it the problem? as the VM is impossible to add the public network @ybaumy
[06:35] <jianghuaw_> s/cloud-config-usl/cloud-config-url/
[06:48] <ybaumy> jianghuaw_: make sure that the network has internet access or access to a apt proxy
[06:49] <ybaumy> jianghuaw_: if 10.14.0.0/24 has no internet access then you must use a apt proxy
[06:50] <jianghuaw_> yes, 10.14.0.0/24 has no internet access.
[06:51] <ybaumy> jianghuaw_: i didnt setup a apt proxy .. i enabled access on the firewall for my networks i use for ports 80/443
[06:52] <jianghuaw_> ok. So iptables may help at here.
[06:53] <ybaumy> jianghuaw_: if your firewall is iptables yes. im using a cisco asa
[06:53] <jianghuaw_> I caught an issue that: disk/by-patch/ip-10.14.0.1:xxxxx-lun-1": Invalid path for Logical Volume.
[06:53] <ybaumy> jianghuaw_: dont know about that
[07:16] <jianghuaw_> Does MAAS support to download squashfs via tftp?
[07:48] <jianghuaw_> ybaumy, I created multiple VMs. Now I shutdown all of the other VMs and only kept one VM. The cloud-init finished successfully. Commissioning passed also:-)
[07:53] <mup> Bug #1674127 changed: delete_authorisation_token is a POST <MAAS:Invalid> <https://launchpad.net/bugs/1674127>
[07:56] <mup> Bug #1674127 opened: delete_authorisation_token is a POST <MAAS:Invalid> <https://launchpad.net/bugs/1674127>
[07:56] <jianghuaw_> ybaumy, actually it should be fixed due the router setup change.
[07:57] <ybaumy> jianghuaw_: thats what i thought
[07:57] <jianghuaw_> yes, thanks for the hint.
[07:57] <ybaumy> jianghuaw_: glad that i could help
[07:59] <mup> Bug #1674127 changed: delete_authorisation_token is a POST <MAAS:Invalid> <https://launchpad.net/bugs/1674127>
[10:21] <BlackDex> Hello there
[10:21] <BlackDex> When i deploy a system, after it is done i get the message "Booting local disk...." "WARN: No MBR magic, treating disk as raw"
[10:22] <BlackDex> And then it hangs
[12:32] <cnf> morning!
[12:43] <pmatulis> morning
[15:05] <cnf> anyone have the MAAS cli only installed on a system?
[15:37] <cnf> so it seems maas doesn't bring up my interfaces properly... sometimes?
[15:50] <cnf> hmm, yeah
[15:50] <cnf> maas randomly doesn't bring up some interfaces o,O
[15:53] <cnf> roaksoax: where you helping with that last week?
[15:53] <cnf> i don't recall exactly
[15:58] <cnf> or maybe it was jamespage ?
[16:14] <pmatulis> cnf, specific symptoms?
[16:16] <cnf> pmatulis: it's vlan's, if i ssh to it, and do an ifdown enp3s0f0 and then ifup enp3s0f0 all the vlans come uo
[16:16] <cnf> they are in /etc/network/interfaces
[16:16] <cnf> but sometimes, they don't come up
[16:21] <pmatulis> cnf, maybe there is something non-optimal about the existing config (/e/n/i). do you know if that's the case? trying to isolate ubuntu-specific problem from a maas problem
[16:21] <pmatulis> pastebin an example config maybe
[16:21] <cnf> pmatulis: it looks sane
[16:22] <cnf> pmatulis: https://bpaste.net/show/4ff14160e0d0
[16:29] <mup> Bug #1674407 opened: [2.2] Spurious error in UI after installing power management dependencies <MAAS:New> <https://launchpad.net/bugs/1674407>
[16:40] <pmatulis> cnf, i don't have anything to add. hopefully someone else does
[16:41] <pmatulis> but at least we have better info to provide them now
[16:45] <cnf> k, thanks anyway
[16:55] <pmatulis> cnf, did you check logs? seem the node logs should contain something
[16:56] <cnf> pmatulis: yeah, nothing that i can see that would explain this