[03:14] <thumper> axw: ping
[03:14] <axw> thumper: PONG!
[03:15] <thumper> axw: do you have a few minutes to talk though the uniter fix you proposed?
[03:15] <axw> thumper: sure
[03:15] <thumper> axw: https://plus.google.com/hangouts/_/canonical.com/arghh-run-sucks?authuser=1
[03:15] <axw> hehe
[04:07] <thumper> axw... hmm... not looking good just now, seems like the tests are hanging
[04:11] <thumper> axw: hmm...
[04:11] <thumper> ran the uniter tests by themselves and all is good
[04:12] <thumper> did hit two other problems with the whole test suite
[04:12] <thumper> one was a weird tear down failures in cmd/jujud where everything paniced because a mongo session was already closed
[04:12] <thumper> and the other is the peergrouper tests failing with Go 1.5
[04:13]  * thumper tries to write a failing test
[04:19] <thumper> UniterSuite.TestUniterUpgradeConflicts intermittent failure
[04:19] <thumper> hazaah
[04:19] <thumper> NOT
[04:23] <thumper> axw: confirmed here too that this fixes the bug as presented
[04:23] <axw> thumper: cool
[04:24] <thumper> axw: now the hard bit, write a failing test with the current code that the code fixes :)
[04:35]  * thumper afk to collect a child
[04:43] <anastasiamac> thumper: the panic in cmd/jujud due tot he closed session is fixed
[04:43] <anastasiamac> well, i have the fix but m waiting for master to land...
[04:44] <anastasiamac> *for master to un-block that is...
[04:52] <thumper> good to know
[05:06] <thumper> hey git folks, is there a way to git stash some of the changed files?
[05:07] <thumper> or interactive stash, like bzr shelve?
[05:12] <anastasiamac> thumper: git stash
[05:12] <anastasiamac> :D
[05:24] <mup> Bug #1498746 opened: azure: units fail to attach block storage <azure-provider> <storage> <juju-core:Triaged by axwalk> <juju-core 1.25:Triaged by axwalk> <https://launchpad.net/bugs/1498746>
[05:27] <mup> Bug #1498746 changed: azure: units fail to attach block storage <azure-provider> <storage> <juju-core:Triaged by axwalk> <juju-core 1.25:Triaged by axwalk> <https://launchpad.net/bugs/1498746>
[05:30] <thumper> axw: Your change which I approve, and my test: http://reviews.vapour.ws/r/2735/
[05:30] <thumper> test confirmed failed before the good change
[05:30] <axw> thumper: looking
[05:32] <axw> thumper: sorry to be annoying, but can you delete the TODO(fwereade) at the top of Uniter.RunCommands? I forgot to delete it while I was there
[05:33] <thumper> axw: ah yes, was meaning to do that
[05:33] <mup> Bug #1498746 opened: azure: units fail to attach block storage <azure-provider> <storage> <juju-core:Triaged by axwalk> <juju-core 1.25:Triaged by axwalk> <https://launchpad.net/bugs/1498746>
[05:34] <axw> thumper: LGTM, thanks. I'll take care of updating master later on
[05:34] <thumper> axw: ok, I'll fix 1.25
[05:34] <thumper> should be same fix
[05:37]  * thumper done now, 
[08:31] <frobware> voidspace, ping - can we catch up sometime today.
[08:32] <voidspace> frobware: sure
[08:32] <voidspace> frobware: after standup?
[08:33] <frobware> voidspace, possibly. clashes with dooferlad, but we can discuss in standup
[08:34] <voidspace> frobware: ah, it's Wednesday
[08:34] <voidspace> frobware: feels like a monday
[08:34] <voidspace> frobware: ok, at your convenience
[08:34] <voidspace> frobware: I'm here all day...
[08:34] <voidspace> frobware: now is good for me if you're free, otherwise later
[10:49] <mup> Bug #1498859 opened: juju.InitJujuHome should not have side effects <juju-core:New> <https://launchpad.net/bugs/1498859>
[11:15] <wwitzel3> sinzui: I'm stumped
[11:16] <wwitzel3> sinzui: exact revision using quickstart on that bundle .. no issues in half a dozen tries
[11:19] <mup> Bug #1498869 opened: doc/backup_and_restore.txt describes deprecated backup plugin <juju-core:New> <https://launchpad.net/bugs/1498869>
[11:55] <rogpeppe> mgz: ping
[11:56] <rogpeppe> sinzui: ping
[12:02] <axw> anastasiamac perrito666: standup?
[12:05] <perrito666> brt
[12:28] <mup> Bug #1497297 changed: TestFindToolsExactInStorage fails for some archs Again <blocker> <ci> <precise> <regression> <test-failure> <unit-tests> <juju-core:Fix Released by cherylj> <https://launchpad.net/bugs/1497297>
[12:34] <mup> Bug #1497297 opened: TestFindToolsExactInStorage fails for some archs Again <blocker> <ci> <precise> <regression> <test-failure> <unit-tests> <juju-core:Fix Released by cherylj> <https://launchpad.net/bugs/1497297>
[12:38] <mattyw> rogpeppe, yeah, I tried that :(
[12:40] <mup> Bug #1497297 changed: TestFindToolsExactInStorage fails for some archs Again <blocker> <ci> <precise> <regression> <test-failure> <unit-tests> <juju-core:Fix Released by cherylj> <https://launchpad.net/bugs/1497297>
[12:43] <mup> Bug #1496997 changed: TestErrorReadingEnvironmentsFile calls chmod on win <ci> <regression> <unit-tests> <windows> <juju-core:Fix Released by cherylj> <juju-core 1.25:Fix Released by cherylj> <https://launchpad.net/bugs/1496997>
[12:43] <mup> Bug #1498869 changed: doc/backup_and_restore.txt describes deprecated backup plugin <juju-core:Invalid> <https://launchpad.net/bugs/1498869>
[12:44] <rogpeppe> mattyw: hrmph
[12:45] <mattyw> rogpeppe, master is unblocked thought - you should be able to go for it now?
[12:46] <rogpeppe> mattyw: ah, cool
[12:46] <mup> Bug #1496997 opened: TestErrorReadingEnvironmentsFile calls chmod on win <ci> <regression> <unit-tests> <windows> <juju-core:Fix Released by cherylj> <juju-core 1.25:Fix Released by cherylj> <https://launchpad.net/bugs/1496997>
[12:46] <mup> Bug #1498869 opened: doc/backup_and_restore.txt describes deprecated backup plugin <juju-core:Invalid> <https://launchpad.net/bugs/1498869>
[12:49] <mup> Bug #1496997 changed: TestErrorReadingEnvironmentsFile calls chmod on win <ci> <regression> <unit-tests> <windows> <juju-core:Fix Released by cherylj> <juju-core 1.25:Fix Released by cherylj> <https://launchpad.net/bugs/1496997>
[12:49] <mup> Bug #1498869 changed: doc/backup_and_restore.txt describes deprecated backup plugin <juju-core:Invalid> <https://launchpad.net/bugs/1498869>
[12:52] <mup> Bug #1496997 opened: TestErrorReadingEnvironmentsFile calls chmod on win <ci> <regression> <unit-tests> <windows> <juju-core:Fix Released by cherylj> <juju-core 1.25:Fix Released by cherylj> <https://launchpad.net/bugs/1496997>
[12:52] <mup> Bug #1498869 opened: doc/backup_and_restore.txt describes deprecated backup plugin <juju-core:Invalid> <https://launchpad.net/bugs/1498869>
[12:56] <bogdanteleaga> sinzui, mgz: can you mark this as closed? https://github.com/juju/juju/issues/3179
[12:57] <sinzui> bogdanteleaga: Done
[12:57] <bogdanteleaga> thanks
[12:58] <mup> Bug #1496997 changed: TestErrorReadingEnvironmentsFile calls chmod on win <ci> <regression> <unit-tests> <windows> <juju-core:Fix Released by cherylj> <juju-core 1.25:Fix Released by cherylj> <https://launchpad.net/bugs/1496997>
[12:58] <mup> Bug #1498869 changed: doc/backup_and_restore.txt describes deprecated backup plugin <juju-core:Invalid> <https://launchpad.net/bugs/1498869>
[12:59] <perrito666> editor with completion and checking plus compiling mongo, this computer is about to bail on me
[13:04] <mup> Bug #1498904 opened: outdated lp:juju-core branch <juju-core:New> <https://launchpad.net/bugs/1498904>
[13:10] <mup> Bug #1498904 changed: outdated lp:juju-core branch <juju-core:Fix Released by sinzui> <https://launchpad.net/bugs/1498904>
[13:22] <mup> Bug #1498904 opened: outdated lp:juju-core branch <juju-core:New> <https://launchpad.net/bugs/1498904>
[13:28] <mup> Bug #1498904 changed: outdated lp:juju-core branch <juju-core:New> <https://launchpad.net/bugs/1498904>
[13:30] <mbruzek> frobware: I think I am seeing the same problem as 1491592
[13:30] <frobware> mbruzek, which is good...
[13:31] <mbruzek> frobware: Are you unable to reproduce?
[13:31] <mbruzek> frobware: I added a comment to https://bugs.launchpad.net/juju-core/+bug/1491592
[13:31] <mup> Bug #1491592: local provider uses the wrong interface <charmers> <customer-support> <kvm> <local-provider> <networking> <juju-core:In Progress by frobware> <juju-core 1.24:Triaged> <https://launchpad.net/bugs/1491592>
[13:31] <mup> Bug #1498904 opened: outdated lp:juju-core branch <juju-core:New> <https://launchpad.net/bugs/1498904>
[13:32] <frobware> mbruzek, I could not reproduce. were you able to reproduce based on the git repo I cloned/
[13:33] <mbruzek> frobware: no I did not clone a repo, I was just working on some stuff and noticed the problem today.
[13:33] <frobware> mbruzek, I noticed in the original description that "There was no reboot of any of his systems."
[13:33] <mbruzek> frobware: Yes I believe that is correct, unfortunately my reproduction was involving a reboot
[13:34] <frobware> mbruzek, either way there's obviously an issue here. Your repro is a lot quicker/easier
[13:35] <mup> Bug #1498904 changed: outdated lp:juju-core branch <juju-core:Fix Released by sinzui> <https://launchpad.net/bugs/1498904>
[13:35] <mbruzek> frobware: I still have the error environment up.  Do you want any additional information before I destroy-environment?
[13:36] <frobware> mbruzek, please could you add your environment info/setup to the bug report
[13:36] <frobware> mbruzek, I see "-e kvm" but don't know what the setup really is.
[13:36] <mbruzek> frobware: absolutely, you want my environments.yaml for that environment?  And what else?  Any log files or other information?
[13:37] <frobware> mbruzek, ahh... is this repro on 1.24.5?
[13:37] <frobware> mbruzek, yes to environments.yaml.
[13:40] <mbruzek> frobware: all-machines.log ?  I can not get to the docker system any longer to get that machine log file
[13:40] <frobware> mbruzek, on the KVM node did you add a bridge? https://jujucharms.com/docs/devel/config-KVM#kvm-guest-network-bridge
[13:41] <perrito666> what is the process to add a feature flag?
[13:43] <mbruzek> frobware: I don't remember adding a bridge but I do see lxcbr0 in my interface listing.
[13:44] <mbruzek> Is it possible that was created by lxc ?
[13:44] <mbruzek> where kvm != lxc ?
[13:45] <frobware> mbruzek, oh certainly
[13:45] <frobware> mbruzek, when you said "Restart the KVM host" which machine is that?
[13:45] <mbruzek> my laptop
[13:45] <mbruzek> I was using these two charms yesterday and restarted, tried to continue to use them today
[13:46] <mbruzek> but I could not ssh to the docker/0 charm
[13:52] <mbruzek> frobware: in any case I can still get to the nagios kvm machine, and it has network access
[13:52] <mbruzek> frobware: do you need anything else before I destroy the environment?
[13:56] <frobware> mbruzek, nope & thanks
[13:58] <natefinch-afk> perrito666: you're assuming there's a process
[14:47] <mup> Bug #1498942 opened: UniterSuite.TestRunCommand fails on windows <blocker> <ci> <regression> <test-failure> <unit-tests> <windows> <juju-core:Incomplete> <juju-core 1.24:Triaged> <https://launchpad.net/bugs/1498942>
[14:49] <sinzui> hi katco bug 1495591 (the master bug of 1498942) is a regression in 1.24 There is a trivial fix already in master that can fix 1.24
[14:50] <mup> Bug #1495591: TestRunCommand fails on windows <blocker> <ci> <regression> <test-failure> <windows> <juju-core:Fix Released by cmars> <juju-core 1.24:Triaged> <https://launchpad.net/bugs/1495591>
[14:53] <natefinch> sinzui: pretty sure she's out for the rest of the week
[14:53] <sinzui> ouch
[14:53] <xwwt> sinzui: I will see who should take it
[14:54] <sinzui> thank you natefinch : thumpr will find work for himself if it isn't resolved in a few hours
[14:55] <natefinch> sinzui:  I can backport the fix listed in the bug, if we want
[14:56] <sinzui> natefinch: that is preferrable to rolling back. I think the fix is trivial to apply
[14:56] <natefinch> sinzui: wicked trivial
[15:02] <mup> Bug #1498942 changed: UniterSuite.TestRunCommand fails on windows <blocker> <ci> <regression> <test-failure> <unit-tests> <windows> <juju-core:Incomplete> <juju-core 1.24:Triaged> <https://launchpad.net/bugs/1498942>
[15:04] <bogdanteleaga> does anybody have "extensive" knowledge of how proxies work in juju?
[15:05] <mup> Bug #1498942 opened: UniterSuite.TestRunCommand fails on windows <blocker> <ci> <regression> <test-failure> <unit-tests> <windows> <juju-core:Incomplete> <juju-core 1.24:Triaged> <https://launchpad.net/bugs/1498942>
[15:05] <natefinch> bogdanteleaga: probably not
[15:05] <natefinch> bogdanteleaga: I know we've had customers complaining that we obey the OS's proxy settings too much... which I find amusing
[15:08] <natefinch> sinzui: it's working: https://github.com/juju/juju/pull/3357
[15:08] <sinzui> thank you natefinch
[15:11] <bogdanteleaga> natefinch: any idea if there are proxy settings being obeyed right at the first connection to the state machine? and if so, how?
[15:11] <mup> Bug #1498942 changed: UniterSuite.TestRunCommand fails on windows <blocker> <ci> <regression> <test-failure> <unit-tests> <windows> <juju-core:Incomplete> <juju-core 1.24:Triaged> <https://launchpad.net/bugs/1498942>
[15:14] <mup> Bug #1498942 opened: UniterSuite.TestRunCommand fails on windows <blocker> <ci> <regression> <test-failure> <unit-tests> <windows> <juju-core:Incomplete> <juju-core 1.24:Triaged> <https://launchpad.net/bugs/1498942>
[15:15] <natefinch> bogdanteleaga: I really don't know the details, would have to dig into the code.
[15:15] <natefinch> bogdanteleaga: I know we've had customers complain that they can't customize the port that the state server listens on, so they have to open their firewall for the port we've chosen
[15:17] <voidspace> natefinch: ping
[15:17] <mup> Bug #1498942 changed: UniterSuite.TestRunCommand fails on windows <blocker> <ci> <regression> <test-failure> <unit-tests> <windows> <juju-core:Incomplete> <juju-core 1.24:Triaged> <https://launchpad.net/bugs/1498942>
[15:17] <natefinch> voidspace: sup?
[15:17] <voidspace> natefinch: got a couple of minutes spare to help me with a problematic transaction?
[15:17] <alexisb> natefinch, thanks for stepping up to help w/ https://launchpad.net/bugs/1495591
[15:17] <mup> Bug #1495591: TestRunCommand fails on windows <blocker> <ci> <regression> <test-failure> <windows> <juju-core:Fix Released by cmars> <juju-core 1.24:Triaged> <https://launchpad.net/bugs/1495591>
[15:19] <natefinch> alexisb: merging 3 line changes is my specialty ;)
[15:19] <alexisb> :)
[15:19] <natefinch> voidspace: sure
[15:22] <voidspace> natefinch: I sent you a pm with the details
[15:23] <voidspace> no reason it should be a pm really though
[15:23] <voidspace> this assert: http://pastebin.ubuntu.com/12531747/
[15:23] <voidspace> always causes this failure: &errors.errorString{s:"cannot set addresses of machine 0: state changing too quickly; try again soon"}
[15:23] <voidspace> and I'm wondering why...
[15:24] <voidspace> omitempty is set, so I wonder if a missing value would be the problem
[15:24] <voidspace> but putting an arbitrary assert that should always pass also seems to trigger the same problem
[15:24] <voidspace> so I suspect I'm missing something fundamental
[15:25] <natefinch> I think it's a problem with the transaction code in mgo
[15:26] <natefinch> voidspace: as I said in DM it's probably a copy of this bug: https://bugs.launchpad.net/juju-core/+bug/1334773
[15:26] <mup> Bug #1334773: Upgrade from 1.19.3 to 1.19.4 cannot set machineaddress <landscape> <lxc> <maas-provider> <precise> <regression> <upgrade-juju> <juju-core:Fix Released by axwalk> <juju-core 1.20:Fix Released by axwalk> <https://launchpad.net/bugs/1334773>
[15:26] <voidspace> natefinch: :-/
[15:26] <voidspace> natefinch: thanks
[15:27] <natefinch> you might ask niemeyer if he's around today.
[15:27] <voidspace> natefinch: we have some tests that actually expect that error (not for machine address but contention tests)
[15:29] <natefinch> voidspace: this looks like the error: https://github.com/juju/txn/blob/master/txn.go#L41
[15:29] <voidspace> natefinch: right, thanks
[15:29] <voidspace> natefinch: so it's an error that we're raising
[15:30] <voidspace> natefinch: that makes me think it's likely to be my fault
[15:30] <voidspace> more debugging needed
[15:30] <perrito666> Bbl
[15:32] <mup> Bug #1498968 opened: ERROR environment destruction failed: destroying storage: listing volumes: An internal error has occurred (InternalError) <destroy-environment> <juju-core:New> <https://launchpad.net/bugs/1498968>
[15:32] <natefinch> voidspace: that error is caused by too many of ErrTransientFailure, which is only ever returned here, AFAICT: https://github.com/juju/juju/blob/6c929a78879c396a2a244caad99851375984e7f8/state/service.go#L129
[15:34] <voidspace> natefinch: I thought it meant that the transaction had failed too many times
[15:34] <voidspace> hmmm
[15:35] <natefinch> voidspace: well, yes
[15:35] <voidspace> there's no service.Destroy involved here, that's for sure
[15:37] <natefinch> voidspace: oh yeah, it looks like if you get txn aboirted too many times, it will return that error
[15:37] <natefinch> voidspace: misread a loop
[15:38] <voidspace> yeah, I just don't see why that transaction would fail - I'm just asserting that the field I'm changing hasn't been changed by anything else
[15:41] <voidspace> natefinch: found it
[15:41] <voidspace> natefinch: it's specified as "bson:,omitempty"
[15:41] <voidspace> natefinch: needed to avoid a migration
[15:41] <voidspace> natefinch: but causes the transaction to fail the first time I set the value - comparing a missing value against an empty address fails
[15:41] <voidspace> hmmmm
[15:42] <voidspace> that's tricky
[15:50] <voidspace> natefinch: so I can assert that the field is either unchanged *or* missing, and that works
[15:51] <natefinch> voidspace: ahh, there you
[15:51] <natefinch> go
[16:21] <frobware> dooferlad, did you come to any conclusion w.r.t. containers and spaces?
[16:22] <dooferlad> frobware: still testing, but it looks like EC2 containers are broken.
[16:23] <dooferlad> frobware: have created bug 1498982
[16:23] <mup> Bug #1498982: failed configuring a static IP for container "1/lxc/0": cannot allocate addresses: instId not supported <juju-core:New> <https://launchpad.net/bugs/1498982>
[16:29] <frobware> dooferlad, voidspace: the order of args to `subnet add' seems awkward to me. I want to do something like: juju subnet add dmz $(get-me-some-subnet-ids) ...
[16:30] <voidspace> frobware: we wanted space to be an optional argument, not sure if that was a factor
[16:30] <voidspace> so subnets default to the default space
[16:31] <frobware> voidspace, I wonder which is the common case though: adding to [default], or something very explicit.
[16:33] <frobware> voidspace, on EC2 If I get "cannot run instances: Request limit exceeded" is there something I can do ... ?
[16:35] <mup> Bug #1498982 opened: failed configuring a static IP for container "1/lxc/0": cannot allocate addresses: instId not supported <juju-core:New> <https://launchpad.net/bugs/1498982>
[16:38] <mup> Bug #1498982 changed: failed configuring a static IP for container "1/lxc/0": cannot allocate addresses: instId not supported <juju-core:New> <https://launchpad.net/bugs/1498982>
[16:41] <frobware> dooferlad, any idea about working around EC2 "cannot run instances: Request limit exceeded"
[16:41] <mup> Bug #1498982 opened: failed configuring a static IP for container "1/lxc/0": cannot allocate addresses: instId not supported <juju-core:New> <https://launchpad.net/bugs/1498982>
[16:43] <dooferlad> frobware: seems like the canonical account has enough people hammering it that we are hitting the request limit. Unfortunately it seems like the solution is to ask Amazon to up the limit for us.
[16:44] <dooferlad> frobware: which the account holder can do, but I am not sure who that is. You could try joey on the Canonical IRC server
[16:44] <dooferlad> http://docs.aws.amazon.com/AWSEC2/latest/APIReference/query-api-troubleshooting.html#api-request-rate
[16:44] <dooferlad> http://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html
[16:44] <dooferlad> :-(
[16:45] <dooferlad> frobware: strange thing is that I am not hitting that message and I am using the canonical account on some machines in eu-central-1
[16:47] <voidspace> frobware: sorry, just seen this
[16:47] <voidspace> frobware: or "that"
[16:54] <dooferlad> voidspace: Could you take a quick look at https://bugs.launchpad.net/juju-core/+bug/1498982 and post any insights?
[16:54] <mup> Bug #1498982: failed configuring a static IP for container "1/lxc/0": cannot allocate addresses: instId not supported <juju-core:New> <https://launchpad.net/bugs/1498982>
[16:54]  * dooferlad reaches EOD
[16:55] <voidspace> dooferlad: oh yuck
[16:55] <voidspace> dooferlad: have to look at it tomorrow I think
[16:55] <frobware> voidspace, dooferlad: thanks. seems like a transient thing, have a machine booted now.
[16:55] <dooferlad> voidspace: thanks. We need to hammer on getting everything EC2 working before next week (I think frobware would like his demo to work)
[16:56] <voidspace> heh
[16:56] <voidspace> dooferlad: I can do some spelunking in the code
[16:56] <frobware> voidspace, dooferlad: +(a lot)
[16:56] <dooferlad> right, I detect a daughter. See you all tomorrow.
[16:56] <voidspace> dooferlad: I think something recent must have broken it, this was working fine
[16:56] <voidspace> o/
[16:56] <voidspace> I'm EOD too
[16:57] <voidspace> the good news is that my transaction works and I have race condition tests that pass (and also fail with the Assert commented out)
[16:57] <voidspace> just a handful of missing tests for my new network functions and I'm done
[16:57] <voidspace> (I think...)
[17:00] <rogpeppe> sinzui: it looks like this CI build is hung up waiting for an instance (it's been like that for quite a long time now): http://juju-ci.vapour.ws:8080/job/github-merge-juju/4846/console
[17:02] <rogpeppe> sinzui: about 3 hours if the times are to be believed
[17:06] <sinzui> :/
[17:07] <sinzui> rogpeppe: I have seen this before, and this time matches AWS failures we saw else where. I can kill the job, someone will need to re-sibmit
[17:07] <rogpeppe> sinzui: thanks
[18:59] <perrito666> you have got to be kidding me bzr: warning: skipping /home/hduran/Develop/canonical/ppas/branches/juju-mongodb3.0/src/mongo-tools/mongodump (larger than add.maximum_file_size of 20000000 bytes)
[19:03] <perrito666> that is NOT a sane thing to do as a default
[19:07] <sinzui> perrito666: I didn't see that when I attempted to package mongodb3. Are you packaging mongodb or ofr5 mongo-tool
[19:07] <sinzui> mongo-tools
[19:07] <perrito666> I am packaging mongodb3 with tools (which implies you bundle the binaries
[19:07] <sinzui> perrito666: Lp wont let you
[19:07] <sinzui> a source package only contains sources, not binaries
[19:08]  * perrito666 sighs and curses an different things
[19:09] <sinzui> perrito666: In general, if a human cannot audit the content of a package and change it, the packge will not be accepted.
[19:09] <perrito666> sinzui: I am just making a ppa for my personal use are those covered by the same rules?
[19:09] <sinzui> perrito666: I already asked jamespage for advice about reconciling the massive change between mongo 2.4 and 3.0.1
[19:10] <perrito666> sinzui: so I pretty much have managed to smash 3 into juju-mongodb
[19:10] <sinzui> perrito666: you can get away with it in your PPA.
[19:10]  * sinzui did the same to provide elastic-search java deps
[19:11] <perrito666> sinzui: cool, my plan is to build the whole migration tool using the ppas as a way to prove the whole thing works
[19:11] <perrito666> and then we can build decent packages
[19:11] <sinzui> +1
[19:11] <perrito666> we will need a juju-mongodb2.6 and juju-mongodb3 which can live next to the current juju-mongodb and, now I learn, also mongo-tools
[19:11] <perrito666> or we could do juju-mongodb3 extra smart and compile both things
[19:12] <perrito666> I am just completely aware that my juju-mongodb3 is not production level so I didnt bother make it all that nice
[19:13] <sinzui> perrito666: yeah, the co-installable issue is one of the many issues I asked for help with
[19:14] <perrito666> the scons options have changed a lot too
[19:15] <perrito666> and the overal layout of the code for the matter I dont really understand how is it that their .deb is bundled with the tools but their root of repo does not build the package with them
[19:17]  * perrito666 buys a bottle of gin and sits in a table with sinzui to cry about their ordeal packaging mongo
[19:19] <perrito666> you might notice too that wiredTiger will not build in 386 and that there is a mistery option(s) to be tweaked so it compiles in willy, apparently there are issues witht he new gcc and some threading feature default aaand also I think it doesnt build in trusty unlest we provide different boost libs :p
[19:23]  * perrito666 reads the news and decides to change the brand of his next car
[19:44] <natefinch> sinzui: I think the build bot is stuck
[19:45] <natefinch> mgz ^
[19:46] <natefinch> perrito666: heh, no VW for you eh?
[19:46] <sinzui> natefinch: again? me looks
[19:48] <sinzui> natefinch: I aborted the stuck job and re-enqueded it. AWS has failed to provide instances several times today :(
[19:52] <natefinch> sinzui: cool. Maybe my merge into 1.24 will happen sometime today, then.  I was wondering why it hadn't merged in 5 hours
[19:55] <sinzui> natefinch: master has been slow to test for the same reason. I am retesting the last job now. So I hope your branch merges, then  CI starts the test of 1.24
[19:57] <perrito666> natefinch: well I was considering a VW up
[19:57] <perrito666> but I might reconsider :p
[19:57] <perrito666> then again, its not like I never commented a test myself :p
[19:58] <natefinch> lol
[20:00] <mup> Bug #1498349 changed: juju upgrade fails with tools upload error due to invalid series "wily" <precise> <streams> <upgrade-juju> <wily> <juju-core:New> <https://launchpad.net/bugs/1498349>
[21:31] <perrito666> finalllyyyy
[21:31] <mwhudson> juju code should be able to import encoding now /cc rogpeppe
[21:31] <mwhudson> (gccgo-go is fixed in trusty-updates)
[21:46] <alexisb> wwitzel3, pint
[21:47] <alexisb> ping
[21:47] <wwitzel3> alexisb: pong
[21:48] <alexisb> heya wwitzel3
[21:48] <alexisb> I was just checking in on this bug: https://bugs.launchpad.net/juju-core/+bug/1498481
[21:48] <mup> Bug #1498481: HAProxy charm broken by recent commit <blocker> <charm> <ci> <haproxy> <quickstart> <regression> <juju-core:Incomplete> <juju-core 1.25:Triaged by wwitzel3> <https://launchpad.net/bugs/1498481>
[21:48] <alexisb> any progress today?
[21:49] <wwitzel3> alexisb: nope, I'm completely stuck on it, I've looked through the logs of the re-run and it didn't lend any help
[21:49] <wwitzel3> alexisb: I can't reproduce locally against the same revision using that bundle, have tried it against aws and maas
[21:50] <wwitzel3> alexisb: there has to be some variable i'm missing in attempting to reproduce, since it happens every time in CI
[21:51] <wwitzel3> alexisb: but I'm stumped, I've managed to get some other bug fixes while thinking on this one, which isn't much, since they aren't block beta1
[21:52] <alexisb> wwitzel3, ack, let look at doing a hand-off w/ thumper's team given it is there start of day
[21:52] <alexisb> maybe fresh eyes will help
[21:57] <thumper> wwitzel3: hey, off my call now and available to chat
[21:58] <thumper> wwitzel3: looking at alexisb's initial attention grab, thinking "yeah, I need a pint about now"
[21:58] <wwitzel3> thumper: haha
[21:59] <wwitzel3> thumper: so I've updated the lp bug with the steps sinzui gave me at the call yesterday for running the juju-ci bundle
[21:59] <thumper> wwitzel3: did you want a quick hangout?
[21:59] <wwitzel3> thumper: sure
[22:00] <thumper> wwitzel3: https://plus.google.com/hangouts/_/canonical.com/we-hate-haproxy
[22:08] <perrito666> anyone is familiar with what is required to add a feature flag besides adding it to feature/flags.go?
[22:10] <alexisb> perrito666, thumper is
[22:10] <alexisb> but he is busy in a hangout w/ a pint
[22:11] <perrito666> and here I am with just wather
[22:19] <thumper> perrito666: that is all that is required, just add a constant, and start checking against it in code
[22:19] <thumper> very easy
[22:19] <perrito666> thumper: wow, I would have expected more boilerplate, just by adding a constant featureflags.Enabled(blah) will be true?
[22:20]  * perrito666 is distrustful of easy things
[23:10] <perrito666> thumper: I am not getting my feature flag enabled, in cmd/jujud/bootstrap.go is it supposed to work that way?
[23:11] <thumper> flags aren't magically set
[23:11] <thumper> you have to set them in tests
[23:11] <perrito666> thumper: tests I am setting it in the env
[23:11] <perrito666> I am trying to hide a feature inside a flag
[23:12] <thumper> you can't set the env and expect it to work :)
[23:12] <thumper> look for "initialFeatureFlags"
[23:12] <perrito666> ahaa
[23:12] <thumper> eg s.SetInitialFeatureFlags(feature.DbLog)
[23:14] <perrito666> thumper: I am not trying to use this inside a test :)
[23:15] <thumper> quck review for someone http://reviews.vapour.ws/r/2741/diff/#
[23:15] <thumper> perrito666: oh? IRL?
[23:15] <perrito666> thumper: yup
[23:15] <thumper> perrito666: where?
[23:15] <thumper> perrito666: what is your exact command?
[23:17] <perrito666> thumper:  I am trying to hide bootstraping into mongo3 behind a feature flag so I went to cmd/jujud/bootstrap.go -> Run() and check if the flag is set before starting mongo so for it I set "mongo3" flag as a const and exported it in my env  as JUJU_DEV_FEATURE_FLAG=mongo3
[23:17] <perrito666> then I juju bootstrap
[23:18] <thumper> I'm fairly sure that the jujud process picks up feature flags early
[23:20] <thumper> perrito666: FLAGS not FLAG
[23:20] <perrito666> thumper: I set both
[23:20] <perrito666> I wasnt sure
[23:20] <thumper> osenv/vars.go
[23:23] <perrito666> thumper: yes, I could have grepped too
[23:23] <perrito666> but anyway, there are not available at that stage, bummer
[23:23] <thumper> which stage?
[23:23] <thumper> it is
[23:23] <thumper> there is an init function in cmd/jujud
[23:24] <thumper> that sets the flags based on the env var
[23:25] <perrito666> there is, wtf is wrong then?
[23:27] <thumper> sinzui: ping
[23:28] <thumper> sinzui: looking at bug 1498481 and http://reports.vapour.ws/releases/3090/job/aws-quickstart-bundle/attempt/1055 as mentioned in comment https://bugs.launchpad.net/juju-core/+bug/1498481/comments/2
[23:28] <mup> Bug #1498481: HAProxy charm broken by recent commit <blocker> <charm> <ci> <haproxy> <quickstart> <regression> <juju-core:Incomplete> <juju-core 1.25:Triaged by wwitzel3> <https://launchpad.net/bugs/1498481>
[23:28] <thumper> sinzui: the logs don't have debug information
[23:29] <thumper> sinzui: oh, you hit the dreaded positional arg bug
[23:30] <thumper> sinzui: please put the --debug after the quickstart not before
[23:33] <thumper> wwitzel3: if you are still around, can you send me the bundle they use?
[23:34] <thumper> I don't have it
[23:34] <thumper> perrito666, waigani, davechen1y: can someone please rubberstamp http://reviews.vapour.ws/r/2741/ ?
[23:37] <waigani> thumper: shipit
[23:39] <thumper> cheers