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