=== CyberJacob is now known as CyberJacob|Away
[03:10] <Lord_Set> Hello
[03:21] <bigjools> hello
[03:30] <Lord_Set> How was your weekend?
[03:31] <bigjools> surprisingly good!
[03:31] <Lord_Set> Awesome. I see the current MAAS build is still broken :P
[03:32] <bigjools> it should not be
[03:32] <bigjools> I tested one on Friday
[03:32] <bigjools> but, welcome to the bleeding edge :)
[03:32] <Lord_Set> I just updated and getting the same amd64/generic is not a valid option error
[03:33] <bigjools> package version?
[03:33] <Lord_Set> Let me check
[03:34] <bigjools> r2101 or later should be ok
[03:35] <bigjools> 1.5+bzr1977+2105+246~ppa0~ubuntu14.04.1 is the very latest (r2105)
[03:35] <Lord_Set> maas_1.5+bzr1977+2105+246~ppa0~ubuntu14.04.1 is what it updated to
[03:36] <Lord_Set> Wondering if it didn't update the config files
[03:36] <bigjools> let me try it here, give me 10 minutes
[03:36] <Lord_Set> Ok
[03:47] <bigjools> Lord_Set: yes, it's screwed.  Grarh.
[03:47] <bigjools> go back to r2101
[03:47] <Lord_Set> Will do
[03:48] <Lord_Set> Should i do a purge or uninstall and then reinstall 2101 fresh?
[03:49] <bigjools> ummm should be able to just install 2101
[03:49] <bigjools> downgrade
[03:52] <bigjools> I think that one's broken too, hang on
[03:52] <Lord_Set> Ok
[03:56] <bigjools> well this is odd, I went back to 2101 which I know was working on Friday, and it;s not working now.  Hm
[03:56] <Lord_Set> 2098?
[04:12] <bigjools> I think another dependency change broke things, it might take a while to work this out
[04:13] <Lord_Set> Alright :(
[04:13] <Lord_Set> Guess I will be doing some manual installs tonight
[04:13] <bigjools> I'm still looking at it
[04:13] <bigjools> don't panic
[04:14] <Lord_Set> lol I don't panic
[04:14] <Lord_Set> I just have 3 servers I need to get up tonight
[04:15] <bigjools> 2101 is working
[04:15] <bigjools> just tested it
[04:15] <Lord_Set> Awesome! Thanks :)
[04:18] <Lord_Set> https://launchpad.net/~maas-maintainers/+archive/dailybuilds/+build/5668409
[04:18] <Lord_Set> ?
[04:20] <bigjools> yes
[04:21] <Lord_Set> Cool, just wanted to make sure it was the correct one. There isn't a separate amd64 build is there? Or are they all i386?
[04:22] <bigjools> they're not arch-specific
[04:22] <Lord_Set> Cool
[04:22] <bigjools> just happen to be built on i386
[04:22] <bigjools> it's all python
[04:47] <Lord_Set> How is the versioning for apt-get set? Trying to install on another server and apt-get install maas=1.5+bzr1977+2101+246~ppa0~ubuntu14.04.1 and various other different attempts aren't working.
[04:47] <bigjools> not working how?
[04:48] <bigjools> that version is no longer published in the PPA so apt-get won't find it
[04:48] <Lord_Set> Saying the verison isn't found
[04:48] <Lord_Set> apt-cache isn't showing the previous versions either
[04:48] <bigjools> it won't, no
[04:48] <bigjools> the archive cleans up quickly in PPAs to save space
[04:48] <bigjools> I am about to push a new build
[04:48] <Lord_Set> Oh ok
[04:49] <bigjools> give me a few moments
[04:49] <Lord_Set> Sure
[04:49] <bigjools> give it about 30 minutes
[04:49] <Lord_Set> Will do
[04:50] <bigjools> https://code.launchpad.net/~maas-maintainers/+recipe/maas-daily-trusty
[04:50] <bigjools> will show up on there
[04:55] <Lord_Set> Thanks for pushing the new build
[05:46] <Lord_Set> this is odd... trying to add a new public ssh key and it keeps telling me it is invalid...
[05:46] <Lord_Set> i have tried through the web interface and cli
[06:55] <bigjools> Lord_Set: it should be fixed, but if you have a problem please describe what you're doing
[06:57] <Lord_Set> Updated from 2101 to 2106. Attempted enlistment and received the same architecture detection issue as before, which results in enlistment failing. The error received is 'amd64/generic' is not valid. The only valid choices are 'amd64, 'i386', and 'arm'.
[06:57] <Lord_Set> I just purged and reinstalled MAAS. Attempting enlistment now as we speak.
[07:01] <bigjools> oh hmmm I think this is a different problem
[07:01] <bigjools> and known
[07:01] <bigjools> https://bugs.launchpad.net/maas/+bug/1289485
[07:01] <ubot5> Ubuntu bug 1289485 in MAAS "MAAS failing to enlist nodes in the Lenovo lab" [Critical,Triaged]
[07:02] <bigjools> I don;t know when this will be fixed, probably late Wednesday
[07:02] <bigjools> unless I find time to look tomorrow (my tomorrow)
[07:02] <Lord_Set> Alright. Which version should I roll back to then?
[07:03] <bigjools> not so easy here since it's mingled with other fixes you might need
[07:05] <bigjools> I'll see what I can do to fix it
[07:05] <bigjools> trunk is in a lot of flux right now
[07:10] <Lord_Set> I have noticed :P
[07:11] <Lord_Set> Don't sweat it
=== CyberJacob|Away is now known as CyberJacob
=== CyberJacob is now known as CyberJacob|Away
=== dannf` is now known as dannf
[14:17] <melmoth> anyone using maas in _large_ deployment ? I got a customer complaiing that "juju destroy-relation" does nothing.
[14:17] <melmoth> like, no error message no nothing.
[14:17] <melmoth> and a couple of days later he told me "heyyy, the relation is removed now, we touch nothing since"
[14:18] <melmoth> so i m wondering, may be when deployng things in real life size , removing relation is suppose to be processed in a matter of... days ?
=== sputnik1_ is now known as sputnik13net
=== CyberJacob|Away is now known as CyberJacob