[02:59] <bitgandtter> good nigth everyone
[02:59] <bitgandtter> there is any document about how to deploy juju on rackspace infrastructure?
[03:45] <JoseeAntonioR> marcoceppi: ping, I think it's done, I'll be around for a couple more hours :)
[04:44] <JoseeAntonioR> marcoceppi: hey, you coming downstairs?
[11:49] <cargill> trying to run juju test, I get ' does not exist in ~/.juju/environments.yaml' or when specifying the current environment using -e, says it is already bootstrapped, so I need an environment but not have it bootstrapped?
[12:11] <cjohnston> hazmat: is this any better: http://paste.ubuntu.com/6986642/ http://paste.ubuntu.com/6986643/
[12:12] <hazmat> cjohnston, yes.. thanks..
[12:13] <cjohnston> hazmat: do you need anything else from it before I trash it?
[12:13] <hazmat> cjohnston, btw.. just needed deployer run output and machine-0.log not all-machines.
[12:13] <cjohnston> ack
[12:13] <hazmat> cjohnston, let me check on #juju-dev one moment
[12:13] <cjohnston> http://paste.ubuntu.com/6986666/
[12:17] <hazmat> cjohnston, i'm wondering if you picked/sized a larger state server if this issue would go away..
[12:17] <cjohnston> a 1g server isn't good enough? :-(
[12:25] <hazmat> depends on how over subscribed things really are on canonistack
[12:25] <hazmat> it was pretty bad last i looked, not sure what the current state is.
[12:41] <cjohnston> horrible would be the correct word I believe :-)
[13:03] <hazmat> cjohnston, have you run mpstat or top to look at your stolen cpu percentage?
[13:04] <cjohnston> hazmat: no.. the load avg yesterday when I watched it got up to ~3
[13:04] <hazmat> cjohnston,  on a single vcpu system.. that seems high
[13:11] <cjohnston> hazmat: I'll give it a try with a larger bootstrap today
[13:39] <lazyPower> Are we upgrading the image stream information again? I'm getting missing image stream data errors from juju this morning on AWS East AZ
[13:39] <lazyPower> s/East/US East/
[13:55] <lazyPower> ah looks like i missed an update: https://bugs.launchpad.net/juju-core/+bug/1283246
[13:55] <_mup_> Bug #1283246: cannot deploy on 1.17.2 on trusty: error on image-stream <juju-core:Incomplete> <https://launchpad.net/bugs/1283246>
[14:00] <rick_h> lazyPower: yea, get .3
[14:00] <lazyPower> It threw me for a loop. I've seen that error on HPCloud before, but not aws - google sorted me though.
[14:52] <jamespage> lazyPower, I just got that as well - its 1.17.2 client against a 1.17.3 environmnet
[14:53] <lazyPower> jamespage: Yep - the bug sorted me out. I forgot we got a version bump last week that i was dragging feet on upgrading.
[14:53] <lazyPower> Thanks for the follow up though!
[14:54] <jamespage> lazyPower, np
[15:28] <cargill> trying to run juju test, I get ' does not exist in ~/.juju/environments.yaml' or when specifying the current environment using -e, says it is already bootstrapped, so I need an environment but not have it bootstrapped?
[15:34] <vds> is there a way to juju set a new key, a key that is not in config.yaml already?
[15:38] <marcoceppi_> cargill: correct, juju test will do bootstraping for each test
[15:38] <marcoceppi_> vds: you can't create new configuration values for charms on the fly, it has to already exist in config.yaml
[15:44] <mattyw> is it possible to run the juju run command from inside a unit?
[15:45] <nessita> hello! I'm running juju devel (1.17.3-0ubuntu1~ubuntu13.10.1~juju1) and I'm using juju to bootstrap some services for the click-package-index project. With juju we start a solr and a elasticsearch unit. When bootstrapping those I never see the units progressing from the "pending" state. Ouput of juju status, and unit logs are at https://pastebin.canonical.com/105456/
[15:45] <rick_h> mattyw: in the dev releases there's a new 'juju run' command that can do that
[15:46] <mattyw> rick_h, yeah - can that command be run from inside a unit?
[15:46] <rick_h> vds: no, the key has to exist and the charm has to know what to do/change on that key as there's not an explicit connection between the config.yaml and what the charm does
[15:46] <rick_h> mattyw: oh, inside the unit? well it runs the command in the unit
[15:46] <rick_h> like ps or such
[15:46] <rick_h> an example is juju run uptime
[15:49] <cargill> marcoceppi_: and how do I create one? I tried adding "test: type:local admin-sercet: ..." but still says that it's already bootstrapped
[15:50] <marcoceppi_> cargill: well, is that environment bootstrapped?
[15:50] <cargill> no, I just added it to the environments.yaml file
[15:51] <marcoceppi_> cargill: do you have /any/ local environment bootstrapped?
[15:51] <cargill> yes, it's name is local
[15:51] <cargill> *its
[15:51] <marcoceppi_> cargill: you can't bootstrap two local environments at the same time without some tweaking
[15:51] <nessita> re: my issue with unit stuck in pending state, one of the errors show "2014-02-24 15:43:22 ERROR juju runner.go:220 worker: exited "upgrader": cannot read tools metadata in tools directory: open /home/nessita/.juju/local/tools/1.17.3.1-precise-amd64/downloaded-tools.txt: no such file or directory" and when browsing the content of /home/nessita/.juju/local/tools/ there is no folder named 1.17.3.1-precise-amd64, just 1.17.3.1-saucy-
[15:52] <cargill> marcoceppi_: so how can i test stuff then? :)
[15:52] <nessita> is that a known issue? shall I downgrade to 1.17.2?
[15:52] <marcoceppi_> cargill: well, you'll need to either destroy the existing local environment, or make a few tweaks to have two simultaneously bootstrapped local environments
[15:53] <marcoceppi_> nessita: that's something weird, like cloud-init failing, can you pastebin the cloudinit logs?
[15:53] <nessita> yes
[15:53] <marcoceppi_> cargill: also, try running ssh elasticsearch/0 and running sudo apt-get update
[15:53] <marcoceppi_> err, nessita ^^ sorry, cargill
[15:53] <marcoceppi_> nessita: verify those boxes have networking
[15:54] <nessita> marcoceppi_: how can I do that?
[15:54] <marcoceppi_> nessita:  try running ssh elasticsearch/0 and running sudo apt-get update
[15:54] <nessita> ack
[15:58]  * nessita1 internet hiccup
[16:04] <nessita1> marcoceppi_: thanks for the pointer. So, I ssh'd into elasticsearch and confirmed the unit has network connection
[16:05] <marcoceppi_> nessita1: cool, cloud-init logs will help illuminate why git wasn't installed
[16:05] <nessita1> pasting
[16:06] <nessita1> marcoceppi_: http://pastebin.ubuntu.com/6987662/
[16:07] <nessita> marcoceppi_: the issue I see is the mismatch between the tools folder
[16:07] <nessita> /home/nessita/.juju/local/tools/1.17.3.1-saucy-amd64 vs /home/nessita/.juju/local/tools/1.17.3.1-precise-amd64
[16:08] <nessita> the unit expects the latter
[16:08] <nessita> and cloud-init uses the former?
[16:09] <marcoceppi_> the unit and cloud-init should both be using the precise one
[16:12] <marcoceppi_> nessita: this cloud-init from bootstrap node
[16:12] <nessita> marcoceppi_: perhaps is a bug on juju devel tools 1.17.3?
[16:12] <marcoceppi_> nessita: juju ssh elasticsearch/0
[16:12] <nessita> I installed the update this moring
[16:12] <marcoceppi_> and give me the cloud-init log from there
[16:12] <nessita> marcoceppi_: on it
[16:12] <nessita> marcoceppi_: where shall I find the cloud init inside the unit?
[16:14] <marcoceppi_> nessita: somewhere in /var/log
[16:14] <nessita> marcoceppi_: http://pastebin.ubuntu.com/6987690/
[16:14] <nessita> perhaps you need the full content not just the last 10 lines, no?
[16:16] <nessita> let me fix that, sorry
[16:16] <marcoceppi_> nessita: yeah, full content of the ones in /var/log, don't need /var/log/juju
[16:17] <nessita> marcoceppi_: http://pastebin.ubuntu.com/6987710/
[16:17] <nessita> so as you predicted there seem to be some network failure, but when I ssh'd into the unit, apt-get update fetched all the repos
[16:17] <marcoceppi_> nessita: yeah, seems like for some reason it wasn't able to resolve dns at first
[16:17] <marcoceppi_> nessita: so, juju destroy-environment, try bootstrapping/deploying again
[16:17] <nessita> marcoceppi_: thanks, will do
[17:17] <nessita> marcoceppi_: so, I destroyed the env and re-bootstrapped, both agents (solr and elasticsearch) show as started, thanks a lot for your help. One more question though: unit-solr-jetty-0.log and unit-elasticsearch-0.log keep showing:
[17:17] <nessita> 2014-02-24 17:16:46 ERROR juju runner.go:220 worker: exited "upgrader": cannot read tools metadata in tools directory: open /home/nessita/.juju/local/tools/1.17.3.1-precise-amd64/downloaded-tools.txt: no such file or directory
[17:47] <marcoceppi_> nessita: is there a /home/nessita/.juju/local/tools/1.17.3.1-precise-amd64 directory?
[17:48] <nessita> marcoceppi_: no, there is not http://pastebin.ubuntu.com/6988138/
[17:48] <nessita> just 1.17.3.1-saucy-amd64
[17:50] <marcoceppi_> nessita: interesting, wonder why that didnt' get created. What's in 1.17.3.1-saucy-amd64
[17:51] <nessita> marcoceppi_: http://pastebin.ubuntu.com/6988149/
[17:52] <marcoceppi_> nessita: huh, maybe make a symlink to that directory named1.17.3.1-precise-amd64>
[17:52] <nessita> marcoceppi_: can this be "caused" by latest 1.17.3 juju-local?
[17:53] <marcoceppi_> nessita: hard to say, I haven't seen anyone else have problems yet
[17:54] <nessita> marcoceppi_: ok, symlink added -- shall the units pick up the change by themselves?
[17:54] <nessita> or this should "work" on futures bootstraps?
[17:56] <nessita> marcoceppi_: I was getting the ERROR every 3 seconds, now they seem to have stopped
[17:56] <marcoceppi_> nessita: the agents should keep trying
[17:56] <nessita> right
[17:57] <nessita> marcoceppi_: thanks a lot for your help!
[19:04] <webbrandon> hello @ all of you!
[19:07] <marcoceppi_> webbrandon: o/
[19:34] <lazyPower> Need an additional +1 on this MP if anyone has time: https://code.launchpad.net/~stub/charms/precise/postgresql/syslog/+merge/206176  its going to run pretty quick, solid tests unless someone see's something glaring
[20:57] <dpb1> HI -- how do I get revision numbers from the store?  I know juju spits them out in different areas, but I was wanting a more api-ish way?
[20:57] <rick_h_> dpb1: if you query the store you can get the latest version number. e.g. https://store.juju.ubuntu.com/charm-info?charms=cs:precise/juju-gui
[20:58] <dpb1> rick_h_: ah, excellent, that will be fine.
[23:09] <webbrandon> is there a bug with the unit logger?  My install script is running but there is no history in my unit log of the installation.
[23:55] <marcoceppi_> webbrandon: be more specific, what version of juju, how are you trying to log, etc