[05:38] <costal> hi there I'm using MAAS 1.7
[05:38] <costal> with dell blades
[05:38] <costal> I have a few issues with the power on function it doesnt seem to work
[05:38] <costal> not the ipmi or the wake on lan
[05:39] <costal> I'm kind of cheating right now just power on the blade when MAAS is trying to do that
[05:39] <costal> it kind of works but sometimes the status of the node is incorrect for example failed when its already deployed
[05:39] <costal> how can I change the status to whatever I want ?
[06:31] <costal> ey guys this is weird now another server is showing couldn't retrieve dists/trusty/main/binary-amd64/Packages
[06:31] <costal> and I'm unable to install it
[08:22] <mup> Bug #1431721 was opened: The django.test.simple module and DjangoTestSuiteRunner are deprecated <django-1.8> <MAAS:Triaged> <https://launchpad.net/bugs/1431721>
[08:23] <mup> Bug #1431723 was opened: Creating a ModelForm without either the 'fields' attribute or the 'exclude' attribute is deprecated <django-1.8> <MAAS:Triaged> <https://launchpad.net/bugs/1431723>
[08:53] <mup> Bug #1431741 was opened: django.core.exceptions.AppRegistryNotReady: Models aren't loaded yet. when starting MAAS with Django 1.7 <django-1.7> <MAAS:Triaged> <https://launchpad.net/bugs/1431741>
[09:05] <mup> Bug #1431741 changed: django.core.exceptions.AppRegistryNotReady: Models aren't loaded yet. when starting MAAS with Django 1.7 <django-1.7> <MAAS:Triaged> <https://launchpad.net/bugs/1431741>
[09:14] <mup> Bug #1431741 was opened: django.core.exceptions.AppRegistryNotReady: Models aren't loaded yet. when starting MAAS with Django 1.7 <django-1.7> <MAAS:Triaged> <https://launchpad.net/bugs/1431741>
[10:47] <dimitern> any maas guys around?
[10:48] <dimitern> I think I found a serious issue with ipaddresses reserve API, when specifying an explicit address
[10:49] <dimitern> under load, maas api returns no error so juju thinks the address is now reserved, but it's not so - looking at the ipaddresses read list
[10:50] <dimitern> this is 1.7.1 from stable ppa, and I think looking at maas source it happens because there's no lock when requesting to allocate a specific address
[11:11] <mup> Bug #1431820 was opened: npm crashes with npm ERR! Error: No compatible version found: nan@'>=1.6.2-0 <2.0.0-0' <dev-environment> <MAAS:Triaged> <https://launchpad.net/bugs/1431820>
[13:56] <kiko> dimitern, please file a bug so we can fix for 1.7.3
[13:56] <kiko> dimitern, 1.8 should have a real solution to this problem
[13:56] <kiko> rvba, ^^
[13:56] <dimitern> kiko, will do
[13:57] <dimitern> kiko, not quite - what's in 1.8 won't affect this issue I think
[13:57] <kiko> dimitern, we changed the DB isolation mode, so it should break instead of silently failing
[13:58] <dimitern> kiko, ah! good to know - will retest with latest 1.8 then
[14:08] <kiko> costal, hey there
[14:08] <kiko> costal, can we help somehow?
[16:56] <AskUbuntu_> tag on maas "error" | http://askubuntu.com/q/596394
[17:48] <dimitern> rvba, are you around?
[17:48] <rvba> dimitern: yep
[17:49] <dimitern> rvba, hey, I was trying to test 1.8.0 beta1 but there is no 14.04 package in the ppa
[17:50] <rvba> dimitern: 1.8.0~alpha6+bzr3625-0ubuntu1~trusty1 (ppa:maas-maintainers/experimental) ?
[17:50] <rvba> I don't see a beta1 package in the usual PPAs….
[17:51] <dimitern> rvba, ah, ok - I was using your ppa so far, will add experimental now and retry
[17:52] <rvba> cool
[17:53] <dimitern> rvba, kiko mentioned the issue I'm having with static addresses not getting allocated under load (but returning no error, so juju thinks it's fine) is fixed on 1.8 using better db isolation
[17:57] <mup> Bug #1431984 was opened: [API] acquire does not allow for name= <MAAS:New> <https://launchpad.net/bugs/1431984>
[18:00] <rvba> dimitern: should be fixed.  But please file a bug still.  Because we probably want to fix it in 1.7 as well.
[18:02] <dimitern> rvba, yeah, will do; first checking 1.8 and then I'll file a bug for 1.7