[09:56] <dweaver> I'm having a problem in MAAS 1.7.5+bzr3369-0ubuntu1~trusty1 enlisting a Dell poweredge R630 that reports there to be no valid network device during ifconfig and hence can't mount the root device over the network.
[09:56] <dweaver> The machine presents NICs as em1, em2 rather than eth0,eth1.
[09:57] <dweaver> Screenshots here: https://dl.dropboxusercontent.com/u/478290/tmp/Photo%2010-06-2015%2010%2034%2016.jpg
[09:57] <dweaver> and https://dl.dropboxusercontent.com/u/478290/tmp/Photo%2010-06-2015%2010%2034%2034.jpg
[09:57] <dweaver> anyone got any idea what is happening here?
[11:58] <dweaver> Traced it to the intel i40e card and a problem with loading the driver.  Looks like the firmware needs an update.
[11:59] <dweaver> However, diging into this I saw that the enlistment preseed has a hard coded ethernet interface (eth0) which may or may not be the case, e.g. em1,em2 etc.  shouldn't the NIC device be detected rather than assume eth0?
[12:51] <kiko> heya dweaver!
[12:51] <kiko> great to see you around
[12:51] <kiko> dweaver, yes, and that strikes me as a bit odd as I think we work with other NIC names
[12:51] <kiko> dweaver, can you point me to the preseed code so I can get somebody to look at it?
[13:27] <roaksoax> dweaver: good cathc. That's an old piece of code that was used to auto-determine the DNS of the machine, but in fact, now it is deprecated. That being said, it should not affect the enlistment process at all. Do you have console logs?
[13:27] <roaksoax> dweaver: a good test would be for you to remove that line of code (and set ip="") and see whether the machine enlists or not
[13:28] <roaksoax> dweaver: in fact, you can simply delete the whole ip=XYZ
[13:48] <kiko> roaksoax, will you file a bug or drive-by?
[13:48] <kiko> roaksoax, also, I think dweaver traced the issue to a firmware bug
[13:50] <dweaver> kiko, Yep, traced it to a firmware bug, I think, rather than a problem with the preseed.  I found the code in the preseed because I was looking for any references to eth0 in the /etc/maas directory, but as roaksoax says it is unused code now, so no need to raise a bug unless we determine a different cause.
[13:51] <kiko> dweaver, the bug should be raised to kill that code I think :)
[13:51] <dweaver> OK, then, I'll raise a bug then ;)
[14:01] <roaksoax> dweaver: please do!
[14:02] <dweaver> roaksoax, thank you for the help
[14:03] <roaksoax> dweaver: thank you for spotting that one
[19:16] <Mmike> Hi, guys. How do I change apt-cache information that curtin puts into 90curtin-aptproxy? I don't want to use MAAS provided squiddeb but want to use my local apt mirror.
[19:23] <Mmike> that is in relation to https://bugs.launchpad.net/maas/+bug/1460151
[19:28] <kiko> Mmike, hmm
[19:29] <Mmike> kiko, I'm looking for some template file or something, inside /etc/maas, to change, but I'm not finding any...
[19:39] <kiko> Mmike, that's a weird bug, but we should definitely make sure we don't step on each other
[19:40] <kiko> Mmike, do you have a proxy configured in maas' settings?
[19:42] <Mmike> sec, let me see
[19:44] <kiko> Mmike, also, do you have maas-proxy installed?
[19:45] <Mmike> kiko, in fact I do (have configued http proxy in maas' settings)
[19:45] <Mmike> yup, I have maas-proxy, 1.7.2+bzr3355-0ubuntu1~trusty1
[19:46] <kiko> Mmike, I am just wondering if you could remove that config and possibly remove the maas-proxy package
[19:46] <kiko> Mmike, if you could and it resolves your issue, it's a valid workaround
[19:46] <kiko> Mmike, maybe do one and then the other, if that makes sense
[19:49] <Mmike> kiko, I'll sping up local maas server and try it out
[19:49] <Mmike> will let you know
[19:49] <Mmike> just need to get rid of damn btrfs, it's unusable for kvm images
[19:52] <Mmike> s/sping/spin
[22:21] <kiko> Mmike, what kernel version are you having btrfs issues with, just curious?
[22:27] <kiko> Mmike, I use it too