[10:19] <nagyz> I'm seeing very strange behaviours
[10:19] <nagyz> is any developer around or shall I open bugs?
[11:21] <mup> Bug #1522790 opened: MAAS API needs to provide a way to discover which is the default space <MAAS:New> <https://launchpad.net/bugs/1522790>
[11:24] <mup> Bug #1522790 changed: MAAS API needs to provide a way to discover which is the default space <MAAS:New> <https://launchpad.net/bugs/1522790>
[11:27] <mup> Bug #1522790 opened: MAAS API needs to provide a way to discover which is the default space <MAAS:New> <https://launchpad.net/bugs/1522790>
[11:30] <mup> Bug #1522790 changed: MAAS API needs to provide a way to discover which is the default space <MAAS:New> <https://launchpad.net/bugs/1522790>
[11:33] <mup> Bug #1522790 opened: MAAS API needs to provide a way to discover which is the default space <MAAS:New> <https://launchpad.net/bugs/1522790>
[12:11] <Bofu2U> I'm having a hell of a time with trying to provision a chassis of 4 nodes, they keep hitting "task systemd-udevd:287 blocked for more than 120 seconds" :-/ Anyone have any ideas?
[12:58] <nagyz> that suggests some IO not going through
[12:59] <nagyz> are you sure all IO paths are clear?
[12:59] <nagyz> I'll be back in around 40 mins or so
[14:04] <Bofu2U> It should be, but I can troubleshoot whatever I need to
[14:04] <Bofu2U> It's just a single SSD so it shouldn't be blocked at all :-/
[14:07] <nagyz> so you have a node with a single ssd
[14:07] <Bofu2U> correct - 8 of them to be specific, heh
[14:07] <nagyz> and when you try to deploy(?) it gets blocked?
[14:08] <nagyz> any chance that's a fattwin? :)
[14:08] <Bofu2U> just trying discovery right now, tbh.
[14:08] <nagyz> so the initial enrollment?
[14:08] <Bofu2U> hehe, c6100 ;)
[14:08] <Bofu2U> 2 of them
[14:08]  * nagyz has fattwins. a lot. :)
[14:08]  * Bofu2U thinks we should talk more about this
[14:09] <nagyz> so you unpacked the node and then the empty node starts enrollment via PXE?
[14:09] <Bofu2U> nah, I've been reformatting these things for a few weeks
[14:09] <Bofu2U> so I know it works in general
[14:09] <Bofu2U> foreman, openstack fuel, etc
[14:09] <nagyz> sure, but I meant that now it's booting via PXE?
[14:10] <Bofu2U> nah, I've done PXE over several other frameworks in general
[14:10] <Bofu2U> the others sometimes have hang ups, but never static
[14:10] <Bofu2U> always goes away after a reboot or two
[14:10] <Bofu2U> this one won't
[14:10] <nagyz> ok so explain what you mean by "discovery" then
[14:10] <nagyz> for me that would be enrollment
[14:10] <Bofu2U> Sorry - discovery as in the initial PXE boot where it loads the live image and takes inventory of the specs, IPMI creds, etc.
[14:10] <Bofu2U> so it's not "assigned" or "provisioned" yet
[14:10] <Donny2Brave> hi
[14:11] <nagyz> ok, so first it's new (this is enrollment), then it's commissioning (this is when it discovers the hw)
[14:11] <nagyz> so enrollment works fine but comissioning gets stuck?
[14:11] <Bofu2U> enrollment is when it gets stuck, never makes it into the interface
[14:11] <nagyz> ok so during enrollment there's a set of scripts that it runs
[14:11] <Bofu2U> never finishes the enrollment process (apologies on the incorrect verbiage on my end)
[14:11] <nagyz> 7 or 8 of them
[14:12] <nagyz> I'm not a maas developer or anything, just a user myself as well
[14:12] <nagyz> if it were me, I'd try running them separately to see where it gets stuck
[14:13] <Bofu2U> yeah let me try watching the console as it goes through - maybe I'd be able to spot it in general
[14:13] <Bofu2U> Also, it looks to be specific to the chassis
[14:13] <Bofu2U> ... as weird as that sounds ...
[14:14] <Bofu2U> R610s don't have a single problem
[14:23] <Bofu2U> have a theory, testing it real quick
[14:23] <Bofu2U> fingers crossed, heh.
[14:36] <nagyz> let me know
[14:37] <Bofu2U> should know in ~10 min
[15:03] <Bofu2U> 10 minutes in "everything is failing horribly" time, obviously.
[15:12] <Bofu2U> doesn't look like that was it - just wiped the drives to see if maybe the previous data was messing it up
[15:15] <Bofu2U> nagyz: here's the only info I was able to really grab from it: http://screencast.com/t/JeqXcMYSl9EX
[16:32] <nagyz> Bofu2U, maybe a stupid suggestion but would you try with the vivid kernel?
[16:45] <mup> Bug #1522898 opened: "node-interface" API should just be "interface" - to allow devices to use it <juju> <networking> <MAAS:Triaged> <MAAS 1.9:Triaged> <https://launchpad.net/bugs/1522898>
[16:48] <mup> Bug #1522898 changed: "node-interface" API should just be "interface" - to allow devices to use it <juju> <networking> <MAAS:Triaged> <MAAS 1.9:Triaged> <https://launchpad.net/bugs/1522898>
[16:51] <mup> Bug #1522898 opened: "node-interface" API should just be "interface" - to allow devices to use it <juju> <networking> <MAAS:Triaged> <MAAS 1.9:Triaged> <https://launchpad.net/bugs/1522898>
[17:12] <mup> Bug #1522910 opened: Install Trusty w/ EFI Secure Boot enabled fails <MAAS:New> <https://launchpad.net/bugs/1522910>
[17:43] <Bofu2U> nagyz maas doesn't let you use the vivid kernel for enrollment does it?
[17:48] <roaksoax> Bofu2U: it does, but in 1.9
[17:52] <Bofu2U> looks like I'm going to try upgrading to that then heh
[17:53] <Bofu2U> I take it it's not at the point of being able to install through apt yet?
[18:11] <Bofu2U> just got it, here goes nothing
[18:13] <mup> Bug #1522910 changed: Install Trusty w/ EFI Secure Boot enabled fails <curtin:New> <MAAS:Won't Fix> <https://launchpad.net/bugs/1522910>
[18:16] <mup> Bug #1522910 opened: Install Trusty w/ EFI Secure Boot enabled fails <curtin:New> <MAAS:Won't Fix> <https://launchpad.net/bugs/1522910>
[18:19] <mup> Bug #1522910 changed: Install Trusty w/ EFI Secure Boot enabled fails <curtin:New> <MAAS:Won't Fix> <https://launchpad.net/bugs/1522910>
[18:21] <Bofu2U> nagyz sadly no go. Same deal. systemd_udevd:293 blocked for more than 120 sec.
[18:24] <Bofu2U> though now I have a little more info at the top
[18:24] <Bofu2U> udevadm settle - timeout of 120 seconds due to- crap scrolled off.
[19:22] <mup> Bug #1522933 opened: Storage options should be applicable on a per-system or per-batch basisaa <MAAS:New> <https://launchpad.net/bugs/1522933>
[19:46] <mup> Bug #1319644 opened: maas with no arguments gives bad advice <cli> <MAAS:Triaged> <maas (Ubuntu):New> <maas (Ubuntu Trusty):New for lborda> <https://launchpad.net/bugs/1319644>
[19:52] <mup> Bug #1319644 changed: maas with no arguments gives bad advice <cli> <MAAS:Triaged> <maas (Ubuntu):New> <maas (Ubuntu Trusty):New for lborda> <https://launchpad.net/bugs/1319644>
[20:01] <mup> Bug #1319644 opened: maas with no arguments gives bad advice <cli> <MAAS:Triaged> <maas (Ubuntu):New> <maas (Ubuntu Trusty):New for lborda> <https://launchpad.net/bugs/1319644>
[20:55] <mup> Bug #1522965 opened: test_get_size_returns_correct_disk_size_for_raid_10 fails spuriously <tests> <MAAS:Triaged> <https://launchpad.net/bugs/1522965>
[21:01] <mup> Bug #1522965 changed: test_get_size_returns_correct_disk_size_for_raid_10 fails spuriously <tests> <MAAS:Triaged> <https://launchpad.net/bugs/1522965>
[21:04] <mup> Bug #1522965 opened: test_get_size_returns_correct_disk_size_for_raid_10 fails spuriously <tests> <MAAS:Triaged> <https://launchpad.net/bugs/1522965>
[21:07] <mup> Bug #1522965 changed: test_get_size_returns_correct_disk_size_for_raid_10 fails spuriously <tests> <MAAS:Triaged> <https://launchpad.net/bugs/1522965>
[21:10] <mup> Bug #1522965 opened: test_get_size_returns_correct_disk_size_for_raid_10 fails spuriously <tests> <MAAS:Triaged> <https://launchpad.net/bugs/1522965>
[21:46] <mup> Bug #1516170 changed: AMT power driver tests are slow <tests> <MAAS:Fix Released by allenap> <https://launchpad.net/bugs/1516170>
[22:11] <PrincessZoey> Can someone help me with Interface updated.
[22:11] <PrincessZoey> Error: Unable to connect to cluster 'Cluster master' (81f3cd33-ba8a-4df3-a752-6bab04608b4e); no connections available.
[22:11] <PrincessZoey> It has the wrong IP and won't let me change it
[22:15] <PrincessZoey> nevermind, fixed it