[04:02] <mup> Bug #1640671 opened: "No rack controllers can access the BMC of node: <node name>" when using OpenStack nova power driver <maas (Ubuntu):New> <https://launchpad.net/bugs/1640671>
[12:47] <mup> Bug #1640780 opened: Restarting image import leaves boot-resources empty (selection is made but not saved) <MAAS:New> <https://launchpad.net/bugs/1640780>
[14:57] <Braven> Good morning
[14:58] <brendand> Braven, hi
[14:58] <Braven> brendand:how are you
[14:58] <brendand> Braven, i saw you're question last night but it was too late to help, sorry about that
[14:58] <brendand> *your
[15:00] <Braven> brendand: Do vlans work with PXE?
[15:01] <brendand> Braven, they ought to, can you describe what you're seeing?
[15:03] <Braven> brendand:The node is failing on commissioning. It is able to boot to PXE. I can see file loading but it at the helper_*.py is having issue
[15:04] <brendand> Braven, do you have logs?
[15:05] <Braven> brandand:you are wanting the console logs?
[15:07] <brendand> Braven, wherever you see the helper_*.py issue
[15:08] <Braven> brendand: let me try to set the logs up.  So i need to redirect console to a serial over network?
[15:11] <brendand> Braven, if you're using 2.0 there is actually a syslog in /var/log/maas/rsyslog/
[15:12] <Braven> brendand:I am still on 1.9.
[15:21] <brendand> Braven, then no, you would need to get the serial console - or just give a bit more info about the error, exactly what it's saying
[15:31] <Braven> brendan:How do you redirect to serial console. I am able to connect to the server ipmitool and I am getting output but is there away to save it
[15:34] <brendand> Braven, you could just copy and paste, or if you wanted to put it in a file you can use tee
[15:35] <Braven> brendan:okay I will give it a try
[15:36] <Braven> Does anything in conmissioning script need to be changed?
[15:40] <brendand> Braven, i need to see what's wrong first
[15:42] <Braven> so reason it stop writing to the serial
[15:52] <Braven> brendand:sorry this is taking so long. I am still trying to get you the console log.
[15:53] <brendand> Braven, np
[16:16] <Braven> brendand: this is last thing I can see "Loading ubuntu/amd64/generic/trusty/release/boot-initrd........................"
[16:16] <Braven>  when logging console log :
[16:20] <brendand> hmmm. that's interesting
[16:21] <brendand> Braven, which version btw?
[16:21] <brendand> oh, trusty
[16:21] <brendand> yeah
[16:21] <Braven> brendand:So wrote down the error. Url_helper.py[WARNING]: Calling 'http://<subnet gateway>'//
[16:23] <Braven> latest-data/instance-d (caused by <socket.error'>
[16:23] <brendand> Braven, and where's that error?
[16:23] <Braven> errno 111
[16:24] <Braven> brendand:why is it try to connect my gateway IP and not maas server"
[16:26] <brendand> Braven, be good to know which log file that's in
[16:27] <Braven> brendand: I know.
[16:28] <Braven> brendand: What appication do use for connecting to the console
[16:31] <Braven> console=tty0 console=ttyS1,57600n8  should I add this to MAAS under setting-> Global Kernel Parameters?
[16:32] <brendand> Braven, you might need to, yeah
[18:37] <mwenning> Has anyone seen this problem?   MaaS 2.1, I can enlist and commission OK, but deploy dumps all sorts of error messages about cannot fetch files.   I cannot ssh into the node to see what's wrong, looks like it's not configuring the NIC's
[19:39] <mup> Bug #1459892 changed: User SSH Key is not editable <MAAS:Invalid by newell-jensen> <https://launchpad.net/bugs/1459892>
[20:49] <Braven> brendand: I added the our server to our prod deployment network and everything is working now.