[10:35] Is there good text on debugging juju anywhere? I've gone through the Hello World example a few times (wordpress+mysql), and it's never worked. On one machine, it would break while apt was installing packages (specifically, the postfix package was waiting for user input). On my home maschine, I get a bad gateway error from nginx. Some kind of high-level roadmap would be very helpful ("Here are where log files live," "Here's how you downloa === wedgwood_away is now known as wedgwood === defunctzombie_zz is now known as defunctzombie [14:42] jcastro: can you delete this? https://code.launchpad.net/~jorge/charms/precise/docs/trunk It breaks `charm list` [14:45] done [15:28] I am still having a problem with TLS failure. Any ideas? [15:50] marcoceppi, see jitsu search [15:50] rshade98, pastebin? [15:51] pmitros, which version? [15:51] pmitros, ie. juju-core or pyjuju [15:52] hazmat: I see there's a search, but no "list" function, any way to list "reviewed" charms outside of charm list? [15:53] Trying to replace `charm list | grep lp:charms` === makyo_ is now known as Makyo [16:03] marcoceppi, search -h [16:03] marcoceppi, owner:~charmers is cheeky but should hit the majority [16:04] er. owners:charmers [16:04] hazmat: http://paste.ubuntu.com/5619558/ ;) [16:07] marcoceppi, ugh.. the help in jitsu is broken.. try jitsu help search [16:07] hazmat: Ah, thanks that works much better [16:08] marcoceppi, its going to break in a week or two when jujucharms.com gets switch over to its new backend, easy enough to fix though [16:08] hazmat: ack === gianr_ is now known as gianr [16:48] hazmat [16:48] http://paste.ubuntu.com/5619673/ [16:51] rshade98, it looks like you have a cert mismatch, the ca is cached on the client in ~/.juju but the ca cert on the client doesn't match up with the bootstrap'd state server [16:52] Is there a way to only bootstrap the certs [16:52] rshade98, not without a destroy-environment and rebootstrap [16:52] I get a failure with multiple boxes, saying the environment is already bootstraps [16:53] rshade98, did you switch machines? [16:53] rshade98, which ever machine you did the original bootstrap on. you have to copy the whole ~/.juju over [16:53] oh, so it is gone [16:53] the ca cert file that works, is in the one that bootstrapped [16:53] I need to destroy the whole environment huh [16:54] rshade98, in that case destroy && bootstrap is the simplest option [16:54] is that just deleting the bucket in ec2? [16:54] alternatively manually creating a new ca, new cert, and installing it onto the bootstrap server [16:54] I mean s3/ec2 [16:54] rshade98, destroy-environment kills all the machines in the env [16:56] ok, so that just deletes the bucket etc. [17:02] now it won't dial the mongos should upload the certs, kill the machine, add the juju groups to it, and start it [17:41] marcoceppi, https://jenkins.qa.ubuntu.com/view/Precise/view/Precise%20Charms/ looking a lot better. Thanks for getting beating that into shape :-) [17:44] s/getting/ === defunctzombie is now known as defunctzombie_zz [18:50] marcoceppi, you coming out to oakland? [18:51] hazmat: yes [18:51] cool [18:55] marcoceppi, it looks like failures generate false success in some cases [18:55] hazmat: have an example? [18:56] marcoceppi, i thought i did.. but explicitly navigating to the last build looks okay.. i was looking at the wordpress graph test [18:56] which still fails with memcached.. but the test is passing [18:56] but the it does look significantly better [18:57] hazmat: yeah, there's still a few broken tests out there. Some corner cases like juju environment not getting set up properly cause the test to pass [18:58] ooh, I like that jenkins overview of charms :) ec2 and local, very neat [18:58] marcoceppi, the new juju-deployer version is pretty robust and helpful about doing the proper wait for success with streaming change output (jcore only though) [18:59] might be able to feed it the test plans, or massage the test plans into a compatible form [18:59] hazmat: juju-developer? You mean the API stuff? [19:01] marcoceppi, its a tool for deploying complex environments from a yaml/json description.. with inheritance, file value substitution, etc. [19:01] lp:juju-deployer [19:01] we use it quite a bit for openstack [19:02] hazmat: that sounds super sexy. Shouldn't be difficult at all to format the test plans to feed that in [19:13] is juju a per s3 folder environment? [19:14] it seems to alway have conflicts when they share. [19:14] and if so, any idea what the best way to randomize the uuid is === defunctzombie_zz is now known as defunctzombie [20:23] <_mup_> Bug #1174905 was filed: Not possible to deploy local charms [20:40] mramm: hey [20:40] hey [20:40] mramm: [20:41] I've filed a ticket to get the go 1.1 beta into the archive so that we can start building official images with it [20:41] if you want help trying to compile yourself davecheney (dfc) can help (I CCed him on our last e-mail exchange) [20:42] ok [20:42] compile go myself or compile juju? [21:07] is there any way to make the juju commands super verbose [21:34] rshade98: as in -vvv? [21:35] rshade98: though you might be actually looking for juju debug-log which tails the services' logs === jibel_ is now known as jibel === wedgwood is now known as wedgwood_away