2014/08/05/#juju-dev.txt

[00:36] <wwitzel3> davecheney: this is for local
[00:39] <wwitzel3> davecheney: they can connect as machine-0 using the password from .juju agents.conf, but nothing is working for admin.
[00:42] <wwitzel3> davecheney: I will have them try that when they are back online tomorrow though .. using that admin-secret from local.jenv
[00:42] <wwitzel3> thanks :)
[00:47] <davecheney> why is the local provider so weird ?!?
[00:47] <davecheney> it has too many edge cases
[01:29] <wwitzel3> yeah
[03:19] <davecheney> no axw today ?
[05:04] <davecheney> I might have accidentally use the word "shittle" when doing my expenses
[05:04] <davecheney> oh well, i'm sure they know what I mean
=== uru_ is now known as urulama
=== menn0_ is now known as menn0
[05:58] <dimitern> morning all
[06:12] <thumper> menn0: hey, you still around?
[06:58] <TheMue> morning
[06:59] <dimitern> hey TheMue
[07:00] <dimitern> jam, hey, are we about to start?
[07:03] <thumper> dimitern: very soon
[07:05] <dimitern> thumper, i've dialed into the conference from skype, as there's a toll free us number, and i'm also in the hangout for video
[07:06] <thumper> dimitern: niemeyer has just finished up with the docker demo
[07:06] <thumper> people are moving to rooms now
[07:06] <dimitern> right, cool
[07:57] <jam1> hey dimitern
[07:57] <jam1> so I like the idea of "juju deploy —net??? foo,bar,endpoint=baz" or something along those lines.
[07:57] <jam1> Did we change anything for "netzone" vs "network" in the doc already?
[07:57] <jam1> I didn't get a chance to read it today
[07:58] <jam1> I also should be going to the review of openstack charm changes, but I tihnk James was in with mark so that one might be getting moved
[08:04] <dimitern> jam1, just a few sentences, as I'm not sure yet how netzones and subnets will be given at deployment time
[08:07] <mjs0> thumper: I'm here now
=== mjs0 is now known as menn0
[08:15] <menn0> thumper: I'll be aroudn for a while working on a presentation so ping me if you like
[09:16] <j-a-meinel> weird, it won't let me be "jam1" but it will let me be j-a-meinel. I wonder if my machine has been connecting + disconnecting too much and it started blocking me.
=== jameinel is now known as jam
[09:20] <jam> hello
[09:22] <rogpeppe1> jam: hiya :-)
[09:37] <jam> hey rogpeppe1, just trying to figure out what usernames I was able to connect as
[09:37] <rogpeppe1> jam: i realised. just thought i'd reply anyway.
=== psivaa is now known as psivaa-reboot
[10:00] <dimitern> voidspace, hey hey
[10:00] <dimitern> voidspace, any troubles with the networker bug so far?
[10:20] <perrito666> morning
[10:26] <natefinch> mornig
[10:26] <natefinch> morning
[10:30] <mattyw> folks, I'm on call reviewer today so if there's anything you want me to take a look at give me a shout
[10:38] <voidspace> dimitern: hey, yes sorry
[10:38] <voidspace> dimitern: missed your message - but yes I have an issue
[10:38] <tasdomas> hi,
[10:39] <dimitern> voidspace, we can talk about it at the standup in 5m then :)
[10:39] <voidspace> dimitern: ok
[10:39] <voidspace> :-)
[10:39] <tasdomas> has anyone tried deploying services on ec2 with the current trunk of juju? Deploying mongo fails (it tries to connect to itself using a public address and fails to do that)
[10:47] <dimitern> voidspace, standup?
[10:47] <voidspace> dimitern: on my way
[10:48] <voidspace> dimitern: hmmm... trying again
[10:50] <voidspace> dimitern: TheMue: my internet is awful
[10:50] <voidspace> dimitern: TheMue: I may be in and out I'm afraid
[10:50] <voidspace> here for now though
[10:50] <TheMue> voidspace: ok
[11:02] <voidspace> dimitern: TheMue: http://pastebin.ubuntu.com/7960111/
[11:06] <voidspace> dimitern: a.st.EnvironConfig()
[11:06] <voidspace> entity.Jobs()
[11:07] <voidspace> dimitern: "booting system without network configuration"
[11:07] <voidspace> dimitern: possibly my network is now screwed in my vm :-)
[11:07] <voidspace> dimitern: I did take a snapshot
[11:07] <dimitern> voidspace, a.CurrentConfig().Value(agent.ProviderType) can give you the provider type
[11:19] <voidspace> dimitern: with this change, straight away I get "agent-state: started"
[11:19] <voidspace> dimitern: which I didn't before
[11:19] <voidspace> unblocked!
[11:19] <voidspace> dimitern: TheMue: thanks guys
[11:20] <dimitern> voidspace, \o/
[11:20] <voidspace> dimitern: need to confirm it works and that it fixes the bug
[11:20] <voidspace> but progress
[11:38] <dimitern> voidspace, :) yep, as usual
[11:39] <TheMue> voidspace: great
[11:41]  * dimitern needs to step out for ~45m
[11:58] <perrito666> sinzui: ping
[11:58] <sinzui> hi perrito666
[11:58] <perrito666> good morning sir
[12:03] <perrito666> sinzui: I was toying with patches yesterday, trying to run ha test and fix the issue
[12:03] <perrito666> I noticed two things:
[12:04] <perrito666> one, I often get an error which looks a lot like a race condition where the test fails because it tries to do something while still upgrading
[12:04] <perrito666> did this happen to you?
[12:05] <perrito666> the other one is, while checking past runs on jenkins I noticed that there is a not very consistent set of blue and red dots, has this test ever been consistently passing?
[12:05] <sinzui> perrito666, yes, and yes
[12:05] <perrito666> sinzui: sorry If I am not being very clear, I woke up a bit dizzy
[12:06] <sinzui> The test doesn't pass on first try every time, CI will accept a pass if it passes withing 3 tried
[12:07] <sinzui> perrito666, It usually fails because of the upgrade error, but you maye see cases in the ha-backup-restore tests where HA could not be achieved to start the backup :(
[12:07] <perrito666> sinzui: I got those too
[12:07] <sinzui> perrito666, and if juju and clouds were less brittle, we would require the tests to pass in the first try
[12:07] <perrito666> actually when running locally I get that error all the time :(
[12:17] <perrito666> so, last test run actually passed, could we trigger a couple more just in case?
[12:18] <perrito666> isnt there a way to determine if juju is upgrading so we can poll until its ready for ha?
[12:30] <mattyw> dimitern, ping?
[12:31] <mattyw> dimitern, cancel that
[12:31] <perrito666> sinzui: ?
[12:33] <sinzui> perrito666, Yes, I can rerun the tests for the last build-revision id
[12:34] <sinzui> perrito666, the tests are scheduled to run in about an hour when the current build published
[12:34] <perrito666> oh, ok
[12:35] <perrito666> "Nokia N900 modem driver included in mainline " <- the kernel certainly is falling a bit behing on device support
[12:35] <sinzui> perrito666, oh, sorry, the publish job has already removed the last binaries. We need to wait
[12:35] <sinzui> perrito666, once CI goes idle, we can retest as oftena s we like
[12:36] <perrito666> tx sinzui
[12:44] <katco> discovered https://github.com/rakyll/coop (Go concurrency examples) this morning. might be an interesting read.
[12:47] <voidspace> tasdomas: ping
[12:47] <tasdomas> voidspace, pong
[12:48] <voidspace> tasdomas: on July 24th you had an error with local provider
[12:48] <voidspace> FATAL: Could not load /lib/modules/3.13.0-32-generic/modules.dep: No such file or directory
[12:48] <voidspace> tasdomas: did you discover what it was?
[12:48] <tasdomas> voidspace, no - I did not
[12:48] <voidspace> your mention of it in the juju-dev logs is the only reference to that particular error that google can fine
[12:48] <voidspace> http://irclogs.ubuntu.com/2014/07/24/%23juju-dev.txt
[12:48] <voidspace> tasdomas: hah, ok
[12:48] <tasdomas> voidspace, was busy and, tbh, forgot about it
[12:48] <voidspace> now google will have two mentions of it I guess
[12:49] <tasdomas> voidspace ;-]
[12:49] <voidspace> tasdomas: but it went away for you?
[12:50] <tasdomas> voidspace, haven't tried since then
[12:50] <voidspace> tasdomas: ah, ok
[12:50] <tasdomas> voidspace, I can take a look later today and ping you with the result
[12:51] <voidspace> tasdomas: that would be cool
[12:51] <voidspace> tasdomas: networking on my vm is a bit screwed up anyway, so it just be due to that
[12:51] <voidspace> I'm going to revert to a snapshot
[12:59] <voidspace> hmmm, no I took my snapshot too late
[12:59] <voidspace> network configuration is screwed there too
[12:59] <voidspace> time to do some digging
[13:03] <voidspace> helping the wife out, biab
[14:03] <jam> dimitern: we're doing the ipv6 in juju, maas, and openstack. Do you want us to call you on the phone, or just a google hangout?
[14:14] <rogpeppe1> any chance that someone might be able to review this straightforward PR? https://github.com/juju/charm/pull/35
[14:19] <rogpeppe1> dimitern, mgz, voidspace, wwitzel3: ^
[14:20] <ericsnow> natefinch: to make matters worse, the person that introduced the bug is out all week
[14:20] <natefinch> rogpeppe1: must be nice to work on a repo that isn't blocked by the bot ;)
[14:20] <rogpeppe1> natefinch: lol
[14:20] <rogpeppe1> natefinch: our bot is down though
[14:20] <dimitern> rogpeppe1, in a call, sorry
[14:21] <rogpeppe1> natefinch: and i also have a couple of branches blocked by the juju-core bot
[14:21] <rogpeppe1> natefinch: but yes, in theory :-)
[14:22] <rogpeppe1> dimitern: np
[14:22] <rogpeppe1> natefinch: so, given that you're blocked on the bot, you obviously have a few moments to spend on that review :-)
[14:24] <natefinch> rogpeppe1: on the contrary, I'm trying to unblock the bot :)
[14:24] <rogpeppe1> natefinch: fair enough
[14:28] <dimitern> jam, is the next call happening in the same room?
[14:30] <mgz> it's not the bot that's blocked...
[14:30] <mgz> it's that master doesn't pass our own validation
[14:31] <mgz> if you want to land things, you either say on the list that we need to land on a broken master, or we unregress
[14:31] <perrito666> mm I am seeing this pop a lot 2014-08-05 13:59:02 ERROR juju.cmd supercommand.go:323 connection is shut down
[14:43] <mattyw> gsamfira, thanks for making the changes - Hi, I'm Matt by the way
[14:44] <gsamfira> Hi Matt :)
[14:44] <gsamfira> thanks for the review
[14:44] <gsamfira> much appreciated
[14:44] <jcw4> rick_h__: https://github.com/juju/juju/pull/468 is a WIP initial draft of the Actions API
[14:44] <jcw4> rick_h__: if you get a chance can you let me know if this is close to what you were looking for last week?
[14:45] <jcw4> rick_h__: s/Actions API/& documentation/
[15:43] <bodie_> if I can get a brief review on https://github.com/juju/juju/pull/448 it would be much appreciated, I can close the bug if I can land it
[15:43] <bodie_> it's very simple
[15:49] <mgz> bodie_: is there a reason not to use SameContents checker?
[15:50] <mgz> rather than the obtainedIds expectedIds block
[15:50] <bodie_> mgz, ignorance?  :/
[15:50] <bodie_> didn't know I didn't have to roll my own
[15:50] <mgz> 's in github.com/juju/testings/checkers/checkers.go
[15:51] <mgz> -s
[15:51] <bodie_> okay, great
[15:59] <bodie_> mgz, I'm not sure that will work since SameContents does not regard duplicates as a problem
[15:59] <bodie_> in this case, I'm counting appearances of each id
[16:00] <mgz> fair enough
=== viperZ28__ is now known as viperZ28
[17:05] <perrito666> really amazon? io timeout?
[17:06] <wwitzel3> that's how they do
[17:07] <jcw4> perrito666: I'm wondering if it's because of the journaling changes possibly overloading mongo?
[17:07] <perrito666> wwitzel3: ec2 is being especially mean with me
[17:07] <jcw4> perrito666: strike that I was thinking of azure not amazon
[17:09] <wwitzel3> trying to help hackedbellini get his up and running again and we are seeing this error .. http://pastebin.ubuntu.com/7962740/ .. for some reason it cannot connect to the web socket api? (local provider)
[17:11] <hackedbellini> it's not the machine-0 problem anymore, this error is from the other machines (the lxc containers)
[17:13] <perrito666> wwitzel3: perhaps api server is not up, check dmesg and logs for machine 0 you might get jujud-machine-0 respawning a lot trying to get up
[17:21] <natefinch> 29% done on memtest. so slow
[17:21] <natefinch> so far no errors
[17:23] <perrito666> natefinch: welcome back
[17:23] <perrito666> natefinch: 1st pass?
[17:24] <natefinch> yeah, doing both sticks at once to see if anything pops up.
[17:25] <natefinch> my tablet wasn't charged which is why I couldn't get on earlier... so I got the oil changed in my car while it was charging.
[17:25] <perrito666> natefinch: that is slow
[17:25] <perrito666> not you, I mean the memtest
[17:25] <natefinch> it only started a little while ago, I got your email while I was out.
[17:26] <perrito666> natefinch: anyway, if your mem if factory dual channel, the stick not broken will break soon
[17:28]  * perrito666 tried to purchase 2x8sodimm today and the nearest one is 800km away and will be hard to get :p
=== psivaa is now known as psivaa-holiday
[17:37] <natefinch> 44% no errors...
[17:38] <natefinch> I think it takes longer because it only tests two gigs arts a time... so it has to do 8 passes total
[17:42] <perrito666> you should have removed one of the banks, your result would be less certain but the test would take half the time
[17:53] <perrito666> do we have concrete info on why our replica takes so much?
[17:55] <natefinch> takes so much.... what?
[17:55] <perrito666> natefinch: sorry I typed half of what I was thinking
[17:55] <perrito666> do we have concrete information on why each replicaSet takes so long to be ready?
[17:57] <natefinch> mongo.... other than that, no.
[17:57] <natefinch> we should really talk to the mongo guys about it
[17:58] <natefinch> 65% done. still no errors
[17:59] <perrito666> natefinch: does you bug happen on heavy loads?
[18:08] <natefinch> only on boot, seems to be.
[18:09] <natefinch> after I reinstalled it was fine until I rebooted.... I had just installed some updates, but I don't know if that was the cause or not.
[18:09] <natefinch> 85% done
[18:13] <perrito666> well if the ram is broken you should see fs corruption
[18:14] <perrito666> if you dont see fs corruption you might be stumbling into some odd update breakage alghough I guess axw and ericsnow should have also
[18:14] <perrito666> you might want to check the SMART data for you hd
[18:14] <perrito666> or sdd
[18:15] <natefinch> smart was fine last time
[18:15] <natefinch> I have RAM errors in dmesg which is why I thought it was ram....
[18:16] <natefinch> tests done. all tests pass
[18:16] <natefinch> well fuck
[18:17] <perrito666> natefinch: what is a ram error in dmesg? I am curious
[18:18]  * perrito666 remembers natefinch recommending that laptop yesterday
[18:18] <natefinch> hahahahahaha
[18:18] <natefinch> I'll get the message when it finishes booting
[18:22] <natefinch> under a section called total RAM covered: 16334 MB
[18:24] <natefinch> *BAD*gran_size: 64k  chunk_size:32M  num_reg: 10   lose cover RAM: -2M
[18:26] <natefinch> a bunch of those with different sizes, but the bad ones all have negative numbers at the end. ones that don't say bad all have 0 or a positive number
[18:27] <natefinch> no friggin' clue what it actually means besides "bad" and "RAM"
[18:29] <perrito666> ahh I see
[18:29] <perrito666> natefinch: http://velenux.wordpress.com/2014/01/
[18:29] <perrito666> linux
[18:29] <perrito666> natefinch: you might find a better explanation at http://my-fuzzy-logic.de/blog/index.php?/archives/41-Solving-linux-MTRR-problems.html
[18:30] <gsamfira> hmm.. if you are running memtest, you should run multiple passes. We used to do 20h memtest on production servers, just to make sure the memory was fine :). Sometimes we would see errors after a few passes
[18:36] <natefinch> perrito666: interesting
[18:37] <natefinch> I wonder if that is my problem
[18:37] <perrito666> yet, that does not seem to be the cause of your other problem
[18:37] <perrito666> although it might
[18:37] <perrito666> try that and then see if the rest of the machine works properly
[18:38] <perrito666> and in that case you might want to return the ram :p
[18:41] <natefinch> perrito666: now if I can figure out what exactly it is that site is trying to tell me to do
[18:43] <wwitzel3> rogpeppe1: ping?
[18:44] <natefinch> it says to look at /proc/config.gz ... but that doesn't exist
[18:47] <natefinch> cat /process/mtrr says almost the whole 16 gigs is in reg00 .... that seems bad.
[18:47] <perrito666> natefinch: you most likely need to compile a kernel with such option on
[18:48] <natefinch> OK, there is no way the answer to this problem is compile a friggin kernel
[18:48] <perrito666> natefinch: try the one shorter
[18:48] <perrito666> natefinch: dude this is linux, most problems, if poked enough will end up having recompile a kernel for an answer
[18:49] <perrito666> natefinch: http://askubuntu.com/questions/244473/how-and-why-should-i-specify-mtrr-gran-size-mtrr-chunk-size
[18:49] <perrito666> that one seems to be more ubuntu oriented
[18:50] <perrito666> the answer seems to be pretty explanatory
[18:50] <natefinch> OK, how do I add that to my grub config?
[18:51] <perrito666> natefinch: /etc/default/grub
[18:51] <perrito666> append to GRUB_CMDLINE_LINUX_DEFAULT
[18:51] <natefinch> also, how do I know what to specify?  no one seems to answer that part
[18:51] <perrito666> "it appears that the error you see is reported when mtrr sanitizer is unable to choose from several options of memory layout. It should print a list of possible options next to the error message. To make the message to go away, you need to specify something lik"
[18:52] <perrito666> pretty trivial problem....
[18:54] <natefinch> not when there's 100 different choices and the effect is not well understood.  I presume I should pick something that has a small lose cover RAM?
[18:54]  * perrito666 was being sarcastic
[18:54] <natefinch> oh
[18:55] <perrito666> apparently the error should come with a list of possible values
[18:55] <natefinch> and if I can pick anything that doesn't say bad, why can't the computer do that?
[18:55] <perrito666> I guess is a trial and error approach
[18:56] <perrito666> natefinch: well I guess you would not want your computer restarting randomly to try new ram mappings
[18:56] <natefinch> there's a bunch of gran size lines mixed in with the bad ones.... I guess those are the options? it's not at all obvious
[18:56] <perrito666> if you wanted an OS that did that you would use another one :p
[18:56] <perrito666> natefinch: pastebin?
[18:57] <natefinch> if it says num_reg 10 and I only have 7, I guess that's not a valid option?
[18:58] <perrito666> natefinch: well apparently if you eff it up you will get dmesg to tell you what would be better choices
[18:58] <natefinch> I don't have network on the stupid machine... I can boot into a live disk...
[18:59] <natefinch> brb
=== uru_ is now known as urulama
[19:32] <realnatefinch> perrito666, http://pastebin.ubuntu.com/7963815/
[19:33] <realnatefinch> btw I have dmesg logs from the 29th where these things show up and i was able to reboot ok then
[19:33]  * perrito666 looks
[19:33] <realnatefinch> (running on the live USB disk I made last time... one nice thing about this having happened so recently)
[19:33] <perrito666> do you have an nvidia video card?
[19:35] <realnatefinch> yep
[19:37] <perrito666> you might have better results if you use the closed driver
[19:37] <perrito666> but that is just a side note
[19:37] <realnatefinch> oh, yeah, I used to beforeI reinstalled
[19:37] <realnatefinch> just forgot to this time
[19:40] <perrito666> natefinch: could you pastebin your /etc/default/grub ?
[19:43] <realnatefinch> sure
[19:45] <realnatefinch> http://pastebin.ubuntu.com/7963935/
[19:46] <perrito666> realnatefinch: you are using a live linux on that machine right?
[19:46] <perrito666> one last, paste me cat /proc/mttr
[19:49]  * perrito666 doesn't like what he sees
[19:50] <perrito666> if not you can blindly try with gran_size: 128M 	chunk_size: 128M 	num_reg: 7  	lose cover RAM: 206M
[19:50] <perrito666> and check if there is a bios upgrade for your machine
=== uru_ is now known as urulama
[19:51] <realnatefinch> ok
[19:54] <realnatefinch> can you link me to that article again?  I'm on my machine, so don't have it in irc history here
[19:54] <realnatefinch> perrito666,  ^
[19:56] <realnatefinch> nevermind, google found it
[19:56] <perrito666> http://my-fuzzy-logic.de/blog/index.php?/archives/41-Solving-linux-MTRR-problems.html
[19:56] <perrito666> and the ubuntu summary http://askubuntu.com/questions/244473/how-and-why-should-i-specify-mtrr-gran-size-mtrr-chunk-size
[19:59] <realnatefinch> it says to append that to the "boot parameters" ...... where is that?
[19:59] <perrito666> realnatefinch: /etc/default/grub -> GRUB_CMDLINE_LINUX_DEFAULT
[20:03] <realnatefinch> ok rebooting
[20:03] <perrito666> gluck
[20:03] <realnatefinch> ks
[20:03] <realnatefinch> thanks
[20:05] <natefinch> bah.  well, let's see what dmesg says
[20:06] <perrito666> meaning?
[20:08] <natefinch> meaning same problem on startup.  dmesg says same thing - please specify chunk size etc
[20:08] <perrito666> natefinch: did you run update-grub?
[20:09] <perrito666> i dont recall the exact command
[20:09] <natefinch> it's definitely in my grub config
[20:09] <natefinch> oh uh no?
[20:09] <perrito666> good thing is you dont need network for that
[20:12] <natefinch> they're update grub and update grub2.
[20:13]  * natefinch reboots
[20:14] <natefinch> bah
[20:14] <perrito666> bah means no good luck?
[20:16] <natefinch> correct
[20:17] <perrito666> is that factory default ram?
[20:18] <natefinch> yep
[20:18] <natefinch> so the mtrr error is gone
[20:19] <natefinch> but my Ethernet and Wi-Fi still terminate with status 1
[20:19] <perrito666> where is that I did not see it in the dmesg you passed
[20:20] <natefinch> near the bottom, search for eth0
[20:22] <perrito666> mm, I see
[20:22] <perrito666> ifconfig -a shows something?
[20:26] <natefinch> shows wifi and Ethernet as 0 packets and not make as UP or RUNNING
[20:26] <natefinch> s/make/marked/
[20:35] <natefinch> it does have a couple virtual Ethernet adapters that I don't recognize
[20:35] <natefinch> at least I assume veth<garbage> means a virtual Ethernet adapter
[20:36] <perrito666> natefinch: well, what you seem to have is  not a problem with the interfaces but with network manager
[20:36] <natefinch> k
[20:36] <perrito666> which is most likely something you installed
[20:36] <perrito666> the virtual ones are most likely juju local :)
[20:36] <perrito666> or virtualbox
[20:37] <perrito666> v tells me that is virtualbox, bc I think juju local is lxbrt
[20:37] <natefinch> I do have both those things installed
[20:37] <perrito666> so we are close
[20:37] <perrito666> tell me what is the content of /etc/networking/interfaces
[20:37] <perrito666> sorry
[20:37] <perrito666>  /etc/network/interfaces
[20:38] <natefinch> I have /etc/network/interfaces.d/ which is empty but no interfaces file
[20:40] <perrito666> natefinch: what version of ubuntu are you using?
[20:40] <natefinch> 14.04.1
[20:41] <perrito666> mm, as it comes ootb you should have /etc/network/interfaces which contains
[20:41] <perrito666> # interfaces(5) file used by ifup(8) and ifdown(8)
[20:41] <perrito666> auto lo
[20:41] <perrito666> iface lo inet loopback
[20:41] <perrito666> bc, basically your problem here, if I understand correctly is that your networking service is not starting properly
[20:41] <perrito666> and network manager seems to be breaking along
[20:42] <perrito666> and therefore your interfaces remain down
[20:42] <perrito666> you could ifup them by hand but sadly negotiating wpa by hand is harder than negotiating an extension with a loan shark
[20:43] <voidspace> perrito666: you sound like you speak from experience
[20:44] <perrito666> have you tried to buy bonds from my country lately? they are cheaper than candy
[20:44] <natefinch> sudo ifup eth0 says unknown interface eth0=eth0
[20:45] <perrito666> natefinch: try adding what I told you to interfaces and sudo initctl restart networking
[20:45] <voidspace> by sheer coincidence my /etc/network/interfaces file has vanished
[20:45] <voidspace> and I'm attempting to repair networking too
[20:45]  * perrito666 smells a bug
[20:46] <voidspace> perrito666: there is an open bug that the local provider kills networking
[20:46] <voidspace> and I'm working on it
[20:46] <perrito666> lol
[20:46] <voidspace> which is probably why my network is broken
[20:46] <perrito666> you seem to have found the problem
[20:46] <voidspace> perrito666: can you pastebin yours
[20:46] <voidspace> perrito666: that's the result not the cause
[20:46] <voidspace> well, it's the current cause of my broken network yes
[20:46] <perrito666> voidspace: mine?
[20:46] <voidspace> perrito666: /etc/network/interfaces
[20:46] <voidspace> I have none whatsoever
[20:47] <perrito666> voidspace: look 20 lines up
[20:47] <perrito666> I copied its contents here
[20:47] <voidspace> was that the sum total?
[20:47] <perrito666> its 3 lines long
[20:47] <voidspace> heh
[20:47] <voidspace> fair enough, thanks
[20:47] <perrito666> natefinch: ^ you might be on the same page there
[20:48] <voidspace> now to reboot the vm and see if I get a network configuration this time
[20:48] <perrito666> voidspace: you dont need to reboot the machine for that
[20:48] <voidspace> and I do, yay
[20:48] <voidspace> perrito666: no, I want to
[20:48] <voidspace> I can manully start the network service anyway
[20:48] <perrito666> voidspace: lol
[20:49] <voidspace> I want to make sure that when I reboot I have it
[20:49] <perrito666> natefinch: well, apparently if you create your interfaces by hand you get network back
[20:49] <perrito666> mm, this is getting crowded with natefinchs
[20:49] <natefinch__> hey, replacing my /etc/network/interfaces with a valid one and doing sudo ifup eth0 worked
[20:49] <natefinch__> haha
[20:49] <perrito666> natefinch: voidspace just explained that that is actually a bug of juju
[20:50] <natefinch__> OMFG
[20:50] <voidspace> and to be fair, one is more than enough...
[20:50] <perrito666> we seem to be deleting interfaces from computers
[20:50] <natefinch__> well shit
[20:50] <voidspace> natefinch__: https://bugs.launchpad.net/juju-core/+bug/1349635
[20:50] <voidspace> local provider kills networking on the host....
[20:51] <perrito666> mmm, seems to be a bug in lx
[20:51] <perrito666> lxc
[20:51] <voidspace> I don't think so
[20:51] <voidspace> see dimiter's comment further down
[20:51] <perrito666> ah, no dimiter commented something
[20:51] <voidspace> we screw with /etc/network/interfaces
[20:52] <voidspace> and normally that's fine, because we control the machine
[20:52] <perrito666> fuuuu, this happens bc local provider runs with sudo
[20:52] <perrito666> ffff
[20:52] <voidspace> but not for the host on local provider
[20:52] <natefinch__> voidspace: that seems like a colossally stupid idea on local
[20:52] <natefinch__> voidspace: it sort of seems like a terrible idea for manual provider, too
[20:52] <voidspace> natefinch__: so my fix, which I'm struggling to test due to screwed networking, is precisely "don't do that on local"
[20:52] <voidspace> natefinch__: we need to do some of it for a maas fix for legacy reasons
[20:53] <natefinch__> can someone post their /etc/network/interfaces for me?
[20:53] <voidspace> that maybe have already gone away
[20:53] <perrito666> we should at least run local provider machine-0 on a chroot
[20:53] <natefinch__> so I can update mine to what it's supposed to look like
[20:53] <perrito666> if we cannot in a lxc
[20:53] <voidspace> perrito666: it has to be a chroot that can create lxc containers
[20:53] <voidspace> not sure if that's possible
[20:53] <perrito666> voidspace: mm, should with the right config
[20:53] <natefinch__> perrito666: that certainly seems better than letting it muck with the user's configuration
[20:53] <perrito666> # interfaces(5) file used by ifup(8) and ifdown(8)
[20:53] <perrito666> auto lo
[20:53] <perrito666> iface lo inet loopback
[20:54] <perrito666> natefinch__: ^
[20:54] <perrito666> those 3 lines
[20:54] <perrito666> you can skip the first one
[20:54] <natefinch__> perrito666: I had to add stuff about eth0 to get ifup to let me turn on eth0
[20:55] <perrito666> natefinch__: if you add that and then initctl restart networking (or start) and then the same with network manager you will most likely get it running or you will need to reboot
[20:55] <voidspace> natefinch__: just that one worked for me
[20:55] <natefinch__> perrito666: ok
[20:55] <perrito666> natefinch__: for future references when the error in dmesg says exited with 1 is a service, when its the actuall device it throws an ugly memory dump
[20:56] <natefinch__> ok
[20:56] <natefinch__> rebooting
=== natefinch__ is now known as natefinch
[20:57] <natefinch> ahh better
[20:57] <natefinch> well, there goes that workday
[20:57] <voidspace> heh
[20:58] <voidspace> heh
[20:58] <voidspace> oops
[20:58] <natefinch> you would think something somewhere would just say "hey, idiot, you're missing /etc/network/interfaces!"
[20:58] <voidspace> that last up arrow and enter was meant for the terminal
[20:58] <perrito666> I think that the chroot solution deserves further research
[20:58] <voidspace> natefinch: yeah, that would have been really nice
[20:58] <natefinch> like, seriously
[20:58] <perrito666> natefinch: it does
[20:59] <natefinch> where?
[20:59] <perrito666> it says networking service who's only conf file is /etc/network/interface existed with error 1
[20:59] <perrito666> :p
[20:59] <natefinch> :P
[20:59] <natefinch> I'm filing a bug against ubuntuy
[20:59] <natefinch> ubuntu
[20:59] <perrito666> which usually means that interfaces has syntax errors
[20:59] <natefinch> but it doesn't say that
[21:00] <perrito666> natefinch: I said, It means
[21:00] <perrito666> :p
[21:00] <natefinch> it just says exited with 1
[21:00] <natefinch> not "config is missing" or "config has errors"
[21:00] <natefinch> that's effectively like "something went wrong"
[21:00] <natefinch> gotta runy
[21:05] <menn0> perrito666: ping
[21:05] <perrito666> menn0: pong
[21:06] <menn0> perrito666: I wanted to ask you about the "update in progress" messages you were seeing while investigating bug 1351030
[21:06] <menn0> perrito666: quick hangout?
[21:07] <perrito666> menn0: sure, let me fetch my headphones
[21:07] <perrito666> btw, isnt it like the middle of the night for you?
[21:07] <menn0> perrito666: nope it's just after 9am
[21:07] <voidspace> menn0: morning
[21:07] <perrito666> menn0: odd, I usually use your presence as the mark that I have been here too long :p
[21:08] <menn0> voidspace: howdy voidspace
[21:08] <voidspace> o/
[21:08] <menn0> perrito666: maybe you have :)
[21:08] <perrito666> menn0: https://plus.google.com/hangouts/_/canonical.com/moonstone
[21:08] <voidspace> midnight here, but I've got insomnia so working late and sleeping late
[21:08] <perrito666> well I start around 7 and its 18 ok, perhas
[21:27] <voidspace> machine-1: 2014-08-05 21:27:06 ERROR juju.worker runner.go:219 exited "networker": command "lsmod | grep -q 8021q || modprobe 8021q" failed (code: 1, stdout: , stderr: FATAL: Could not load /lib/modules/3.13.0-32-generic/modules.dep: No such file or directory
[21:45] <perrito666> sinzui: ping
[21:46] <perrito666> and since I am here menn0 could you answer my email to juju-dev with the bit that says how to know if juju is upgrading?
[21:48] <menn0> perrito666: will do
[21:48] <perrito666> thank you
[21:49] <perrito666> with that I can ask sinzui to add the wait in the tests :p
[21:53] <voidspace> I give up
[21:53] <voidspace> for now
[21:53] <voidspace> goodnight all
[21:55] <perrito666> voidspace: dont forget to comment on the bug and un-assign it
[23:11] <perrito666> menn0_: all yours added a helper script and decent instructions on how to repreoduce and since we are in it a few of my not so useless conclussions
[23:11] <perrito666> cheers
[23:11] <perrito666> https://bugs.launchpad.net/juju-core/+bug/1351030
[23:16] <menn0_> perrito666: thanks very much. that's very helpful.
=== menn0_ is now known as menn0