/srv/irclogs.ubuntu.com/2014/02/24/#juju.txt

=== CyberJacob is now known as CyberJacob|Away
bitgandttergood nigth everyone02:59
bitgandtterthere is any document about how to deploy juju on rackspace infrastructure?02:59
=== mwhudson is now known as zz_mwhudson
JoseeAntonioRmarcoceppi: ping, I think it's done, I'll be around for a couple more hours :)03:45
=== timrc is now known as timrc-afk
JoseeAntonioRmarcoceppi: hey, you coming downstairs?04:44
=== JoseeAntonioR is now known as jose
=== stub` is now known as stub
=== seelaman` is now known as seelaman
=== thumper is now known as thumper-afk
=== CyberJacob|Away is now known as CyberJacob
=== mthaddon` is now known as mthaddon
=== Geek_Juice is now known as Bryanstein
=== ev_ is now known as ev
cargilltrying 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?11:49
cjohnstonhazmat: is this any better: http://paste.ubuntu.com/6986642/ http://paste.ubuntu.com/6986643/12:11
hazmatcjohnston, yes.. thanks..12:12
cjohnstonhazmat: do you need anything else from it before I trash it?12:13
hazmatcjohnston, btw.. just needed deployer run output and machine-0.log not all-machines.12:13
cjohnstonack12:13
hazmatcjohnston, let me check on #juju-dev one moment12:13
cjohnstonhttp://paste.ubuntu.com/6986666/12:13
hazmatcjohnston, i'm wondering if you picked/sized a larger state server if this issue would go away..12:17
cjohnstona 1g server isn't good enough? :-(12:17
hazmatdepends on how over subscribed things really are on canonistack12:25
hazmatit was pretty bad last i looked, not sure what the current state is.12:25
=== zz_frobware is now known as frobware
cjohnstonhorrible would be the correct word I believe :-)12:41
hazmatcjohnston, have you run mpstat or top to look at your stolen cpu percentage?13:03
cjohnstonhazmat: no.. the load avg yesterday when I watched it got up to ~313:04
hazmatcjohnston,  on a single vcpu system.. that seems high13:04
cjohnstonhazmat: I'll give it a try with a larger bootstrap today13:11
=== mhall119_ is now known as mhall119
=== timrc-afk is now known as timrc
lazyPowerAre we upgrading the image stream information again? I'm getting missing image stream data errors from juju this morning on AWS East AZ13:39
lazyPowers/East/US East/13:39
=== jcsackett_ is now known as jcsackett
lazyPowerah looks like i missed an update: https://bugs.launchpad.net/juju-core/+bug/128324613:55
_mup_Bug #1283246: cannot deploy on 1.17.2 on trusty: error on image-stream <juju-core:Incomplete> <https://launchpad.net/bugs/1283246>13:55
rick_hlazyPower: yea, get .314:00
lazyPowerIt threw me for a loop. I've seen that error on HPCloud before, but not aws - google sorted me though.14:00
=== deej` is now known as deej
=== psivaa is now known as psivaa-afk-bbl
jamespagelazyPower, I just got that as well - its 1.17.2 client against a 1.17.3 environmnet14:52
lazyPowerjamespage: Yep - the bug sorted me out. I forgot we got a version bump last week that i was dragging feet on upgrading.14:53
lazyPowerThanks for the follow up though!14:53
jamespagelazyPower, np14:54
=== bdmurray_ is now known as bdmurray
cargilltrying 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:28
vdsis there a way to juju set a new key, a key that is not in config.yaml already?15:34
marcoceppi_cargill: correct, juju test will do bootstraping for each test15:38
marcoceppi_vds: you can't create new configuration values for charms on the fly, it has to already exist in config.yaml15:38
mattywis it possible to run the juju run command from inside a unit?15:44
nessitahello! 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_hmattyw: in the dev releases there's a new 'juju run' command that can do that15:45
mattywrick_h, yeah - can that command be run from inside a unit?15:46
rick_hvds: 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 does15:46
rick_hmattyw: oh, inside the unit? well it runs the command in the unit15:46
rick_hlike ps or such15:46
rick_han example is juju run uptime15:46
cargillmarcoceppi_: and how do I create one? I tried adding "test: type:local admin-sercet: ..." but still says that it's already bootstrapped15:49
=== psivaa-afk-bbl is now known as psivaa
marcoceppi_cargill: well, is that environment bootstrapped?15:50
cargillno, I just added it to the environments.yaml file15:50
marcoceppi_cargill: do you have /any/ local environment bootstrapped?15:51
cargillyes, it's name is local15:51
cargill*its15:51
marcoceppi_cargill: you can't bootstrap two local environments at the same time without some tweaking15:51
nessitare: 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:51
cargillmarcoceppi_: so how can i test stuff then? :)15:52
nessitais 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 environments15:52
marcoceppi_nessita: that's something weird, like cloud-init failing, can you pastebin the cloudinit logs?15:53
nessitayes15:53
marcoceppi_cargill: also, try running ssh elasticsearch/0 and running sudo apt-get update15:53
marcoceppi_err, nessita ^^ sorry, cargill15:53
marcoceppi_nessita: verify those boxes have networking15:53
nessitamarcoceppi_: how can I do that?15:54
marcoceppi_nessita:  try running ssh elasticsearch/0 and running sudo apt-get update15:54
nessitaack15:54
* nessita1 internet hiccup15:58
=== rektide_ is now known as rektide
nessita1marcoceppi_: thanks for the pointer. So, I ssh'd into elasticsearch and confirmed the unit has network connection16:04
marcoceppi_nessita1: cool, cloud-init logs will help illuminate why git wasn't installed16:05
nessita1pasting16:05
nessita1marcoceppi_: http://pastebin.ubuntu.com/6987662/16:06
=== nessita1 is now known as nessita
nessitamarcoceppi_: the issue I see is the mismatch between the tools folder16:07
nessita/home/nessita/.juju/local/tools/1.17.3.1-saucy-amd64 vs /home/nessita/.juju/local/tools/1.17.3.1-precise-amd6416:07
nessitathe unit expects the latter16:08
nessitaand cloud-init uses the former?16:08
marcoceppi_the unit and cloud-init should both be using the precise one16:09
marcoceppi_nessita: this cloud-init from bootstrap node16:12
nessitamarcoceppi_: perhaps is a bug on juju devel tools 1.17.3?16:12
marcoceppi_nessita: juju ssh elasticsearch/016:12
nessitaI installed the update this moring16:12
marcoceppi_and give me the cloud-init log from there16:12
nessitamarcoceppi_: on it16:12
nessitamarcoceppi_: where shall I find the cloud init inside the unit?16:12
marcoceppi_nessita: somewhere in /var/log16:14
nessitamarcoceppi_: http://pastebin.ubuntu.com/6987690/16:14
nessitaperhaps you need the full content not just the last 10 lines, no?16:14
nessitalet me fix that, sorry16:16
marcoceppi_nessita: yeah, full content of the ones in /var/log, don't need /var/log/juju16:16
nessitamarcoceppi_: http://pastebin.ubuntu.com/6987710/16:17
nessitaso as you predicted there seem to be some network failure, but when I ssh'd into the unit, apt-get update fetched all the repos16:17
marcoceppi_nessita: yeah, seems like for some reason it wasn't able to resolve dns at first16:17
marcoceppi_nessita: so, juju destroy-environment, try bootstrapping/deploying again16:17
nessitamarcoceppi_: thanks, will do16:17
=== seelaman` is now known as seelaman
nessitamarcoceppi_: 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
nessita2014-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 directory17:17
=== hatch_ is now known as hatch
=== roadmr_ is now known as roadmr
marcoceppi_nessita: is there a /home/nessita/.juju/local/tools/1.17.3.1-precise-amd64 directory?17:47
nessitamarcoceppi_: no, there is not http://pastebin.ubuntu.com/6988138/17:48
nessitajust 1.17.3.1-saucy-amd6417:48
marcoceppi_nessita: interesting, wonder why that didnt' get created. What's in 1.17.3.1-saucy-amd6417:50
nessitamarcoceppi_: http://pastebin.ubuntu.com/6988149/17:51
marcoceppi_nessita: huh, maybe make a symlink to that directory named1.17.3.1-precise-amd64>17:52
nessitamarcoceppi_: can this be "caused" by latest 1.17.3 juju-local?17:52
marcoceppi_nessita: hard to say, I haven't seen anyone else have problems yet17:53
nessitamarcoceppi_: ok, symlink added -- shall the units pick up the change by themselves?17:54
nessitaor this should "work" on futures bootstraps?17:54
nessitamarcoceppi_: I was getting the ERROR every 3 seconds, now they seem to have stopped17:56
marcoceppi_nessita: the agents should keep trying17:56
nessitaright17:56
nessitamarcoceppi_: thanks a lot for your help!17:57
=== zz_mwhudson is now known as mwhudson
webbrandonhello @ all of you!19:04
=== mwhudson is now known as zz_mwhudson
marcoceppi_webbrandon: o/19:07
lazyPowerNeed 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 glaring19:34
=== zz_mwhudson is now known as mwhudson
dpb1HI -- 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-gui20:57
dpb1rick_h_: ah, excellent, that will be fine.20:58
=== Guest70848 is now known as wallyworld
=== CyberJacob is now known as CyberJacob|Away
=== hloeung is now known as Guest14965
webbrandonis 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:09
=== Guest14965 is now known as hloeung
=== frobware is now known as zz_frobware
=== zz_frobware is now known as frobware
marcoceppi_webbrandon: be more specific, what version of juju, how are you trying to log, etc23:55

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!