[07:27] <jamespage> gnuoy`, unit test failures on the quantum-gateway dvr merge
[07:28] <gnuoy`> jamespage, ack, I'll take a look
[07:28] <jamespage> gnuoy`, needs some further mocking by the looks of things
[07:33] <jamespage> gnuoy`, nova-compute +1 and merged
[07:34] <gnuoy`> jamespage, fantastic, ta
[07:34] <jamespage> gnuoy`, I added the snippet to the kilo template as I did it
[07:34] <jamespage> libbo but trivial
[07:34] <gnuoy`> kk
[07:45] <jamespage> gnuoy`, one trivial comment on neutron-api - take a look - I've tested it locally with the unit tests - seems OK
[07:45] <gnuoy`> will do, thanks
[07:50] <gnuoy`> jamespage, +1 your proposed change to my neutron-api mp
[07:51] <gnuoy`> jamespage, quantum-gateway unit tests are fixed too
[07:53] <gnuoy`> jamespage, I'd like to talk to you about the neutron-network-service relation in the neutron-openvswitch charm nut we can do that later
[07:53] <gnuoy`> s/nut/bur/
[07:53] <gnuoy`> urgh, typing is hard
[07:57] <jamespage> gnuoy`, sure lets do that in a sec
[08:14] <jamespage> gnuoy`, it seems odd to have nova-cc related to neutron-openvswitch
[08:16] <gnuoy`> jamespage, neutron metadata service needs keystone credentials. So, this operates in the same way as the quantum-gateway charm does. ie its gets keystone creds from nova-cc. However, I do accept that this is really an abuse and suboptimal. Currently, the keystone charm will not issue creds without the client registering an endpoint which neutron-ovs doesn;'t do. I was thinking that the longer term solution here is to amned the keystone charm to allow you
[08:16] <gnuoy`> to join the identity-service relation without specifying an endpoint and get creds back
[08:18] <jamespage> gnuoy`, the alternative is for the neutron-api charm to pass those over?
[08:18] <jamespage> an alternative rather
[08:18] <gnuoy`> jamespage, yes, that would work
[08:19] <jamespage> gnuoy`, that would be preferable to having another relation IMHO
[08:19] <gnuoy`> jamespage, fine by me. I'll make that so
[08:19] <jamespage> gnuoy`, +1
[08:19] <gnuoy`> :q
[08:23] <dosaboy> jamespage: i've done a bit of a refactor of the cred gen code in keystone with the aim of following up with the ability for identity relation to be able to hand out creds without necessarily adding an endpoint
[08:23] <dosaboy> jamespage: gnuoy suggested perhaps a new relation
[08:23] <dosaboy> jamespage: not sure what best approach is yet
[09:47] <apuimedo> gnuoy`: +1 for amending the keystone service
[09:48] <apuimedo> at the moment what I do is use keystone-admin and use keystone client to get my credentials
[09:49] <apuimedo> dosaboy: sounds good ;-)
[09:50] <gnuoy`> apuimedo, yes, I think the keystone charm needs to grow that feature
[09:51] <apuimedo> indeed
[09:53] <apuimedo> gnuoy`: why is nova-api-metadata not run by the nova-cloud-controller charm?
[10:03] <gnuoy`> apuimedo, I am struggling to come up with a sensible reason
[10:04] <apuimedo> ;-)
[10:39] <jamespage> gnuoy`, legacy mode good for review?
[10:39] <jamespage> dosaboy, your keystone refactoring landed btw
[10:39] <jamespage> dosaboy, and some feedback on your hacluster one
[10:39] <gnuoy`> jamespage, just having a moment of doubt as to whether it'll block the packages being installed
[10:40] <jamespage> apuimedo, gnuoy`: re the neutron-api-metadata agent not running on the nova-cc - by placing it on the edges alongside the hypervisors, we avoid a) pushing all traffic to a single set of services a b) avoid having to make them HA as well
[10:41] <gnuoy`> jamespage, but it currently runs on the neutron-gateway
[10:41] <gnuoy`> not on the edges
[10:42] <jamespage> gnuoy`, unless you run novat-network - in which case it does run on the hypervisors
[10:42] <jamespage> gnuoy`, for neutron right now it sits alongside the neutron-metadata agents
[10:42] <jamespage> on the gateway nodes
[10:42] <jamespage> gnuoy`, dvr changes that again right?
[10:42] <gnuoy`> (unless you're using dvr)
[10:42] <gnuoy`> yeah
[10:42] <jamespage> spot on
[10:42] <jamespage> that way the neutron-metadata agent is only dependent on the api service running locally - so its quick
[10:43] <jamespage> and resilient to a whole node failure
[10:43] <jamespage> single service failures can still create problems tho
[10:43] <dosaboy> jamespage: got it thanks, fixing now
[10:44] <apuimedo> ok
[10:44] <apuimedo> thanks
[10:53] <apuimedo> jamespage: why is it that on the quantum-gateway charm
[10:53] <apuimedo> there's only the template for nova.conf for havana but not for icehouse/juno?
[10:53] <jamespage> apuimedo, template loader is os series prioritized
[10:54] <jamespage> the nova.conf in havana is ok for icehouse and juno
[10:54] <jamespage> we only create a new template for a specific OS version if its really required
[10:54] <apuimedo> I thought as much, but I wanted to confirm :P
[10:54] <jamespage> (as for kilo)
[10:54] <apuimedo> on my charms I follow a default on /templates plus overrides in subdirs
[10:54] <jamespage> its on the gateway charm so it can sit alongside neutron metadata proxies in l3 and dhcp namespaces
[10:55] <apuimedo> (if needed)
[10:55] <gnuoy`> jamespage, legacy mode is good for review
[10:55] <jamespage> gnuoy`, ack - doing so now
[10:55] <gnuoy`> ta
[10:55] <apuimedo> jamespage: well, it's there also because nova-api-metadata needs it to exist
[10:55] <apuimedo> right?
[11:00] <jamespage> yeah
[11:10] <jamespage> gnuoy`, merged legacy mode support
[11:10] <jamespage> ta
[11:22] <apuimedo> jamespage: the legacy mode support is so that the charms that are refactored still play nice with those that had relations with the pre-refactor versions?
[11:22] <jamespage> yup
[11:23] <jamespage> we'll leave legacy mode on by default for this release, and then turn of off for 15.07
[11:48] <jamespage> gnuoy`, OK - I think I've reviewed what I can - I'm going to rebase my 0mq branches next
[11:48] <jamespage> gnuoy`, are you looking at le next?
[11:49] <gnuoy`> neutron-oopenvswitch dvr fixes next, then le, was my plan
[12:04] <stub> The charm boilerplate from 'charm create' does a 'pip install charmhelpers'. How does that work with the python-apt dependency? Last I heard, you couldn't install that with pip.
[12:22] <marcoceppi_> stub: you can't, unfortunately, I thought python-apt was installed on the images already?
[12:22]  * marcoceppi_ goes to verify
[13:29] <Odd_Bloke> I'm playing around with the GCE provider in the latest ppa:juju/devel package, and it looks like the boostrap node doesn't have port 17070 opened up to the world.
[13:29] <Odd_Bloke> Is this a known bug?
[14:02] <ericsnow> Odd_Bloke: yep #1436191
[14:02] <mup> Bug #1436191: gce: bootstrap instance has no network rule for API <firewall> <gce-provider> <juju-core:Fix Committed by dimitern> <juju-core 1.23:Fix Committed by dimitern> <https://launchpad.net/bugs/1436191>
[14:03] <ericsnow> Odd_Bloke: already fixed
[14:03] <Odd_Bloke> ericsnow: Any easy way to get the fixed code?
[14:04] <lazyPower> Odd_Bloke: we have a docker container with trunk
[14:04] <lazyPower> aisrael: have you started publishing your nightlies?
[14:05] <Odd_Bloke> lazyPower: Ah, cool; link?
[14:05] <ericsnow> Odd_Bloke: yep, see http://reviews.vapour.ws/r/1282
[14:05] <lazyPower>  Odd_Bloke:   docker run -ti -v $HOME/.juju-trunk:/home/ubuntu/.juju adamisrael/juju-trunk
[14:06] <ericsnow> Odd_Bloke: the key thing is to change the first arg to OpenPorts to env.globalFirewallName()
[14:06] <lazyPower> i'm not sure that has the fix however - confirming with aisreal that he's still tracking nightlies - we just started publishing these last week at our sprint
[14:06] <Odd_Bloke> OK, cool; I'm just playing around so I'll hold off until aisrael confirms.
[14:11] <ericsnow> Odd_Bloke: let me or wwitzel3 know if you have any questions or run into trouble (we wrote the provider)
[15:17] <lazyPower> apuimedo: o/  I understand amulet is giving you some fuss?
[15:18] <marcoceppi_> jcastro: et al can someone look over my answer to see if I can improve it? http://askubuntu.com/questions/603317/is-masas-juju-or-the-charm-responsible-for-ssh-keygen-on-nodes/603381#603381
[15:19] <jcastro> looking
[15:20] <apuimedo> lazyPower: luqas was the one that experienced the issue
[15:21] <apuimedo> he'll be able to detail it better
[15:21] <lazyPower> apuimedo: sure thing :) If i can get the error message and a sneak peek at the test code we should be able to triage/address it
[15:23] <luqas> lazyPower: hi, when trying to use the placement option for deployment in amulet I get an error in juju-deployer
[15:23] <luqas> let me find it
[15:27] <luqas> lazyPower: http://paste.ubuntu.com/10712730/
[15:28] <luqas> but I've seen there was a fix for that in https://bugs.launchpad.net/juju-deployer/+bug/1383336
[15:28] <mup> Bug #1383336: TypeError "takes exactly 2 arguments (4 given)" raised while deploying <cts> <juju-deployer:Fix Committed by freyes> <https://launchpad.net/bugs/1383336>
[15:28] <apuimedo> brb
[15:30] <lazyPower> luqas: do you have juju-deployer installed via pip?
[15:30] <lazyPower> luqas: i do believe this fix was released in the pip package, but has not yet been ported to the repository package. bit of a mismatch atm
[15:33] <luqas> lazyPower: yes, that can be, I have the repository package, will try with the pip one and be back if it still shows, thank you
[15:33] <lazyPower> np
[15:49] <joec1> Hi folks, has anyone got Juju to deploy to subscription in Azure with EA? Either via the VMDepot VM or the Azure CLI tools? I'm having problems.
[15:56] <lazyPower> joec1: i'm not sure i'm parsing what you're asking. EA = Ensure availability?
[15:57] <joec1> Hi @ LazyPowerAzure Sorry I meant with Microsoft Enterprise Agreement
[15:57] <joec1> I'm not sure if that even matters but I can't get Juju to deploy using any documented methods
[15:58] <lazyPower> joec1: yeah, i'm looking here @ the azure EA markeing page and this looks mostly like a pricing structure model, not a different provider setup. So I'm going to make the blanket statement of it should just work
[15:58] <lazyPower> what issue are you running into during bootstrapping?
[16:01] <lazyPower> joec1: can you confirm you were following the instructions located here: bzr merge lp:~canonical-ci-engineering/charms/trusty/logstash/local-tarball
[16:01] <joec1> I'm just attempting starting from scratch again but a few days ago I got the following:
[16:01] <joec1> ERROR failed to bootstrap environment: PUT request failed: BadRequest -  XML Schema validation error in network configuration at line 39,18.  (http code 400: Bad Request)
[16:01] <lazyPower> gah, paste fail
[16:01] <lazyPower> https://jujucharms.com/docs/1.20/config-azure
[16:02] <joec1> yes I followed those instructions (even though there is an error in the openssl generation commands)
[16:02] <lazyPower> joec1: can you file a bug about the openssl generation eror here? https://github.com/juju/docs/issues
[16:02] <joec1> forget the openssl error, that was my fault
[16:03] <lazyPower> i'm bootstrapping now to try and reproduce
[16:04] <lazyPower> joec1: i've found a relevant thread on this bug and it looks like its due to storage configuration
[16:04] <lazyPower> https://bugs.launchpad.net/juju-core/+bug/1304778
[16:04] <mup> Bug #1304778: ERROR PUT request failed: BadRequest - XML Schema validation error in network configuration at line 54,18. (http code 400: Bad Request) <azure-provider> <bootstrap> <juju-core:Fix Released by axwalk> <https://launchpad.net/bugs/1304778>
[16:05] <joec1> brilliant!
[16:05] <joec1> I'll test with trunk, thanks so much
[16:06] <lazyPower> not a problem, i can confirm it bootstraps appropriately on 1.23-beta
[16:06] <joec1> I did see that bug but my eyes jumped over the second reported error - I thought it was just about storage not network
[16:06] <joec1> thanks again
[16:06] <lazyPower> cheers
[16:10] <joec1> ahhh
[16:12] <joec1> I'm using juju 1.22 stable from the repos, that bug was committed to 1.20 I think. Still, will try with 1.23-beta....
[16:12] <lazyPower> I don't believe its a core bug, i may be wrong
[16:12] <lazyPower> it seems strange that I'm able to bootstrap if it were a core bug. I know that azure is a fairly finicky provider - its very particular about how you have it configured
[16:30] <rbasak> strikov: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html
[16:37] <joec1> @lazyPower - I don't suppose you have any easy to follow instructions for building juju trunk do you? I've already hit a problem following instructions in http://bazaar.launchpad.net/~go-bot/juju-core/trunk/view/head:/README
[16:39] <joec1> # launchpad.net/juju-core/testing/filetesting
[16:39] <joec1> ../src/launchpad.net/juju-core/testing/filetesting/filetesting.go:194: cannot use checkers.Satisfies (type check.Checker) as type gocheck.Checker in function argument:
[16:39] <joec1> 	check.Checker does not implement gocheck.Checker (wrong type for Info method)
[16:39] <joec1> 		have Info() *check.CheckerInfo
[16:39] <joec1> 		want Info() *gocheck.CheckerInfo
[16:41] <joec1> apologies for the spam
[16:57] <lazyPower> joec1: i do 1 moment. theres 2 methods you can follow
[16:58] <lazyPower> 1) you can use the dockerbox aisrael is publishing/maintaining of nightly builds
[16:58] <joec1> @lazyPower thanks its ok
[16:58] <joec1> I used github instead of launchpad.net
[16:58] <lazyPower> or 2) you can build from source following a tutorial here: http://marcoceppi.com/2014/11/compiling-juju-core-from-source/
[16:58] <joec1> really appreciate the help thanks! :)
[16:58] <lazyPower> cheers :)
[17:22] <joec1> Fiddlesticks! I get the same error using juju trunk
[17:41] <lazyPower> joec1: lets recap your config
[17:42] <joec1> sure
[17:42] <lazyPower> can you nuke the sensitive bits and pastebin me your config?
[17:42] <joec1> will do
[17:42] <joec1> 1 sec
[17:51] <joec1> @lazyPower http://pastebin.com/GyExhKR5
[17:52] <joec1> shows the error log also. I have to add --upload-tools as it complains: "Juju cannot bootstrap because no tools are available for your environment. You may want to use the 'agent-metadata-url' configuration setting to specify the tools location."
[17:56] <joec1> I've also attempted using "--constraints instance-type=Small" but get the same XML BadRequest error
[17:57] <aisrael> joec1: You need to add a couple options to your ~/.juju/environments.yaml, under the provider you're trying to bootstrap
[17:57] <aisrael> agent-metadata-url: https://streams.canonical.com/juju/tools
[17:57] <aisrael> agent-stream: devel
[17:58] <lazyPower> aisrael: o/
[17:58] <joec1> will try that now thanks @aisrael
[17:58] <lazyPower> aisrael: is your nightly docker image still the go-to place to get trunks code? Odd_Bloke was asking earlier.
[17:58] <aisrael> lazyPower: Yep, it sure is!
[17:58] <lazyPower> Odd_Bloke: ^ seems like you're g2g, aisrael is on the case.
[18:02] <joec1> @aisrael juju can't parse those options in environments.yaml
[18:02] <joec1> "YAML error: line 458: found character that cannot start any token"
[18:03] <aisrael> joec1: What error are you getting? Can you pastebin your environments.yaml (with the sensitive bits removed)?
[18:03] <joec1> here is the one I just made: http://pastebin.com/GyExhKR5
[18:04] <aisrael> which provider are you using?
[18:04] <lazyPower> joec1: apologies for the delay in a conf call - give me a few and i'll be responsive again
[18:04] <lazyPower> aisrael: this is for azure
[18:04] <lazyPower> aisrael: thanks for taking a look
[18:04]  * lazyPower got busy all of a sudden
[18:05] <joec1> :) np really appreciate your help
[18:06] <aisrael> joec1: Based on that error, I suspect you have an error in the lines you just added. They should be added under test-juju01
[18:06] <joec1> yep, that's where i added them
[18:06] <lazyPower> joec1: just for grins can you attempt to bootstrap in teh US West region? i can confirm this is the group i'm using as well - and this may be region specific.
[18:07] <joec1> will do
[18:07] <lazyPower> i see you're using the EU group - if we can isolate that this may be region specific i can get a bug tailored to the issue
[18:10] <joec1> ...creating storage account.....
[18:11] <joec1> same error unfortunately
[18:11] <joec1> I changed my environment.yaml file to reflect the new region and the new storage account created in that region
[18:12] <joec1> region being "West US"
[18:12] <joec1> a couple of things:
[18:12] <aisrael> If you're still getting a yaml parsing error, then there's something wrong with the yaml.
[18:13] <joec1> OK, I didn't try with the agent-stream settings, will do now
[18:14] <joec1> the error I'm getting is this currently: "2015-03-31 18:11:05 ERROR juju.cmd supercommand.go:430 failed to bootstrap environment: PUT request failed: BadRequest - XML Schema validation error in network configuration at line 39,18. (http code 400: Bad Request)"
[18:15] <joec1> OK, juju doesn't like TAB indentation :(
[18:17] <joec1> however, after adding agent-metadata-url: https://streams.canonical.com/juju/tools and agent-stream: "released" I still get the XML Bad request error
[18:18] <joec1> juju status complains that it can't connect to API server without admin-secret
[18:20] <lazyPower> joec1: so you've already bootstrapped, these issues are coming from juju deploy <service>?
[18:20] <joec1> FYI, I'm trying to start a Juju environment in an already set up Azure service that has VMs and local network configured already, could that be the problem?
[18:20] <joec1> no, I haven't bootstrapped at all
[18:20] <lazyPower> that does sound like it could be part of the issue
[18:20] <lazyPower> the existing VM's not so much
[18:20] <lazyPower> but altererd networking - indeed
[18:21] <lazyPower> i would have thought that changing the region to be US West (so long as this was still vanilla networking, et-al) would have been successful. Did those networking changes propigate globally?
[18:22] <joec1> mmm not sure
[18:22] <joec1> i'm not sure how I can check because Azure web portal doesn't appear to differentiate
[18:24] <joec1> I'd imagine the local network config would propagate so VMs can be moved between regions easily
[18:24] <joec1> I've got to go for 30 minutes back soon!
[18:26] <lazyPower> ack, cheers joec1afk
[18:32] <Odd_Bloke> lazyPower: aisrael: The .juju/environments.yaml written out by that Docker container is (a) owned by root:root and (b) has agent-stream at the top level which doesn't appear to apply to an environment manually added.
[18:32] <Odd_Bloke> (i.e. I had to move the agent-stream declaration in to my gce environment mapping)
[18:32] <lazyPower> Odd_Bloke: interesting, we pass a -v to volume mount our $JUJU_HOME which should have copied your local environments.yaml
[18:34] <Odd_Bloke> lazyPower: I actually did (copy-pasting from earlier), -v $HOME/.juju-trunk:/home/ubuntu/.juju.
[18:35] <Odd_Bloke> But I wouldn't have had a config pointing at the devel tools anyway. :)
[18:35] <aisrael> lazyPower: I usually point it to a fresh juju path, as to not trample over an existing environment
[18:36] <lazyPower> wierdness,  #disclaimer - i havent used teh nightly image yet - but this is good feedback if its being silly on volume mounts.
[18:36] <aisrael> Odd_Bloke: I'll take a look at that. I thought I'd fixed the top level thing. :/
[18:38] <Odd_Bloke> aisrael: I exited out of the pretty curses interface (because it didn't have a GCE option).
[18:38] <aisrael> Odd_Bloke: did you exit out of juju-quickstart?
[18:39] <aisrael> Odd_Bloke: ahh. That'd definitely cause the error with agent-stream being nested incorrectly.
[18:39] <Odd_Bloke> aisrael: I did indeed.  #prebugging
[18:41] <aisrael> Odd_Bloke: thanks for that! I've added issues to the project. I'll see to getting those fixed.
[18:42] <Odd_Bloke> aisrael: Thanks!
[18:43] <Odd_Bloke> Next question: I'm trying out deploying Jenkins; I've juju deploy'd, and I have agent-status 'executing' and workload-status 'maintenance'. Should I translate this as "patience, my young padawan"?
[18:48] <joec1> the more I think about my issue the more I think it has something to do with the EA subscriptions
[18:48] <joec1> for example, the Azure Market doesn't work for me in the default Azure portal
[18:50] <Odd_Bloke> OK, I've now got agent-status 'executing' and workload-status 'active', but Jenkins is not running on jenkins/0.
[18:51] <jcastro> I think it's just patience at this point
[18:51] <jcastro> how long has it been?
[18:52] <Odd_Bloke> 2015-03-31 18:43:49 INFO unit.jenkins/0.start logger.go:40  * Starting Jenkins Continuous Integration Server jenkins
[18:52] <Odd_Bloke> 2015-03-31 18:43:49 INFO unit.jenkins/0.start logger.go:40    ...done.
[18:52] <Odd_Bloke> So ~10 minutes.
[18:52] <Odd_Bloke> `sudo service jenkins status` reports "Jenkins Continuous Integration Server is not running"
[18:53] <jcastro> did you deploy the slave too?
[18:54] <Odd_Bloke> Nope; shall I?
[18:54] <jcastro> I assume so, it's what the instructions say
[18:54] <jcastro> "To deploy Jenkins server you will also need to deploy the jenkins-slave charm."
[18:54] <Odd_Bloke> *shuffles feet*  *avoids eye contact*
[18:54] <jcastro> https://jujucharms.com/jenkins/
[18:54] <jcastro> after that you expose it and it should work
[18:58] <joec1> bah, I give up for now, many thank again @lazyPower and @aisrael for offering assistance
[18:59] <Odd_Bloke> Rut roh: http://paste.ubuntu.com/10713842/
[19:00] <Odd_Bloke> I suspect that's a problem with GCE firewalls.
[19:01] <Odd_Bloke> How can I get juju to retry the hook (so I can try to fix it manually)?
[19:03] <tvansteenburgh> juju resolved --retry
[19:13] <Odd_Bloke> OK, I think that failure is happening because the Jenkins server isn't running.
[19:14] <Odd_Bloke> And Jenkins isn't running because of... a buffer overflow. \o/
[19:15] <Odd_Bloke> http://paste.ubuntu.com/10713939/ to be exact.
[19:32] <jcastro> Odd_Bloke, what size is the instance?
[19:35] <Odd_Bloke> jcastro: A GCE g1-small, which only has 1.7GB of RAM.
[19:35] <Odd_Bloke> So that certainly seems a likely culprit.
[19:35] <jcastro> yeah that's my first guess, out of RAM, but that's a guess
[20:41] <Odd_Bloke> ericsnow: wwitzel3: The europe-west1-a zone has been deprecated and removed in GCE, but juju just tried to use it.
[20:42] <ericsnow> Odd_Bloke: it only tries zones that GCE offers (we get a list from the GCE API at runtime)
[20:43] <Odd_Bloke> ericsnow: http://paste.ubuntu.com/10714510/
[20:45] <ericsnow> Odd_Bloke: yeah, dimitern ran into the same thing and we decided not to worry about it since the zone will be gone before 1.23 is released and we only try zones GCE tells us about at runtime
[20:45] <ericsnow> Odd_Bloke: however, it is a pain
[20:46] <Odd_Bloke> Ah, OK, cool.
[20:46] <ericsnow> Odd_Bloke: for now you can use a different region
[20:47] <ericsnow> Odd_Bloke: I imagine this could be a problem in the future if GCE deprecates any other zones
[20:48] <ericsnow> Odd_Bloke: we could add code to filter out known deprecated zones but that is a maintenance burden we didn't want to take on if we didn't have to
[20:51] <Odd_Bloke> ericsnow: The API returns the deprecation info: https://cloud.google.com/compute/docs/reference/latest/zones#resource
[20:53] <ericsnow> Odd_Bloke: thanks for pointing that out, we must of missed it
[20:53] <ericsnow> Odd_Bloke: could you open a bug for this?
[20:55] <Odd_Bloke> ericsnow: I could reopen https://bugs.launchpad.net/juju-core/+bug/1436655 ?
[20:55] <mup> Bug #1436655: gce provider should stop using deprecated zone europe-west1-a <gce-provider> <juju-core:Won't Fix> <juju-core 1.23:Won't Fix> <https://launchpad.net/bugs/1436655>
[20:55] <ericsnow> Odd_Bloke: that would be perfect
[20:55] <ericsnow> thanks
[20:56] <Odd_Bloke> ericsnow: Actually, I can't change the status there; shall I comment and you reopen?
[20:56] <ericsnow> Odd_Bloke: sounds good
[20:59] <ericsnow> Odd_Bloke: done; thanks for looking into this.
[20:59] <Odd_Bloke> ericsnow: No worries; thanks for writing the provider! :)
[20:59] <ericsnow> wwitzel3: could you take a look at #1436655?
[21:00] <mup> Bug #1436655: gce provider should stop using deprecated zone europe-west1-a <gce-provider> <juju-core:Won't Fix> <juju-core 1.23:Won't Fix> <https://launchpad.net/bugs/1436655>
[21:03] <wwitzel3> ericsnow: yeah, I can take a look, I need a break from the CS stuff anyway
[21:03] <ericsnow> wwitzel3: :)
[21:03] <ericsnow> wwitzel3: the fix shouldn't be too bad
[21:06] <Odd_Bloke> jcastro: Jenkins still falls over in the same way on a 12G RAM instance. :(
[21:06] <Odd_Bloke> (And the same version doesn't do so when I run it in a similar GCE instance not via Juju)
[21:29] <jcastro> Odd_Bloke, hmm no clue then, I'm off to dinner so perhaps post to the list?
[21:32] <wwitzel3> ericsnow: I'm only working on one right now, I haven't started on the other yet
[21:32] <ericsnow> wwitzel3: k
[21:33] <ennoble> Is there a way to stop juju from destroying a maas node when no services are deployed to it? I just destroyed the services running on a machine and it seems like it's freed immediately? It's pretty annoying to have to wait 10 minutes for maas to re-deploy the node
[22:09] <wwitzel3> ericsnow: is NewZone purely for testing purposes?
[22:09] <ericsnow> wwitzel3: note sure
[22:09]  * ericsnow take a look
[22:10] <wwitzel3> ericsnow: I don't see it being used anywhere but tests, but just watned to make sure
[22:10] <ericsnow> wwitzel3: yeah, looks like it is just for testing
[22:10] <wwitzel3> ericsnow: I've got a fix, I insept the the deprecatedStatus of the zone and bubble that up via the availZoneUp method, I also annotate the default error if Google suggests a replacement
[22:11] <ericsnow> wwitzel3: cool
[22:16] <ennoble> is there a way to get juju to reread the JUJU_DEV_FEATURE_FLAG env variable or do you have to destroy the environment and re-create it?