=== CyberJacob|Away is now known as CyberJacob
=== gary_poster|away is now known as gary_poster
=== benji_ is now known as benji
=== _mup__ is now known as _mup_
=== _mup__ is now known as _mup_
=== jamespag` is now known as jamespage_realme
=== cmagina_ is now known as cmagina
=== CyberJacob is now known as CyberJacob|Away
=== makyo_ is now known as Makyo
=== gary_pos` is now known as garyposter
=== garyposter is now known as gary_poster
=== hazmat` is now known as hazmat
=== Daviey_ is now known as Daviey
=== jamespag` is now known as jamespage
=== sarnold_ is now known as sarnold
=== markthomas1 is now known as markthomas
=== FunnyLookinHat__ is now known as FunnyLookinHat
[17:26] <arosales> Debug question: I am hitting: agent-state-info: 'hook failed: "config-changed"'
[17:27] <marcoceppi> arosales: charm-tools 1.2.5 made it in to homebrew \o/
[17:27] <arosales> marcoceppi, woot!
[17:27] <arosales> osx users rejoice
[17:27] <arosales> re my debug question
[17:27] <marcoceppi> arosales: someone in the homebrew community helped fix the formula so it wasn't breaking everything
[17:27] <marcoceppi> arosales: shoot
[17:27] <arosales> I am running: juju debug-hooks trac/0 config-changed
[17:28] <arosales> and then: juju resolved --retry trac/0
[17:28] <arosales> in a separate window but now info is being shown in the tmux session
[17:28] <arosales> go homebrew community!
[17:28] <marcoceppi> arosales: close debug-hooks, run it without the hookname
[17:28] <arosales> s/now/now
[17:28] <marcoceppi> juju debug-hooks trac/0
[17:28] <arosales> s/now/no/
[17:30] <arosales> marcoceppi, ok I'll get that a try my previous "retry" seems to have fixed the error
[17:35] <arosales> marcoceppi,  "juju resolved --retry trac/0 " still gives me nothing on my debug tmux when trying to debug  agent-state-info: 'hook failed: "config-changed"'
[17:36] <marcoceppi> arosales: 1.16.5?
[17:36] <arosales> correct
[18:39] <arosales> marcoceppi, beside juju-gui are there any other charm store charms that have tests?
[18:39] <arosales> marcoceppi, I didn't see wordpress with one . . .
[18:39] <marcoceppi> arosales: postgres
[18:40] <arosales> marcoceppi, any of them using amulet?
[18:40] <beuno> noodles775 and sidnei have worked on adding tests to a few charms
[18:40] <beuno> they may know
[18:40] <arosales> beuno, thanks
[18:41] <sidnei> haproxy, squid-reverseproxy, apache2, none using amulet
[18:41] <sidnei> and those are only 'unit' tests, they don't test a juju deployment
[18:42] <arosales> sidnei, gotcha and thanks for the info.
[18:43] <arosales> sidnei, do these charms all function with "juju test"
[18:43] <sidnei> arosales: never tried
[18:45] <marcoceppi> arosales: if they don't have a tests dir, then now
[18:45] <arosales> sidnei, ok and thanks for the info.  We are working on charm testing infrastructure with juju test looking in test sub dir. So we'll see how these tests arehandled
[18:45] <marcoceppi> no*\
=== lamont` is now known as lamont
[18:46] <sidnei> marcoceppi: they have a hooks/tests dir fwiw
[18:46] <lazypower> have the docs for testing juju charms been updated?
[18:47] <marcoceppi> lazypower: no :(
[18:47] <lazypower> marcoceppi: Hit me up later this week and I'll lend a hand.
[18:47] <marcoceppi> sidnei: if you made a file in tests/00-unittest you could have that bash script execute the unit tests in hooks/tests
[18:47] <sidnei> marcoceppi: definitely
[18:47] <arosales> sidnei, ah I see that for apache2 charm (ie hooks/tests/*)
[18:48] <lazypower> I need to write tests for the errbit charm - may make for some good documentation coming from someone completely new to the system. We'll record it and transcribe into docs?
[18:48] <marcoceppi> sidnei: that'd be a great test to include in addition to fucntional tests
[18:48] <marcoceppi>  /me loves unit testing
[18:55] <marcoceppi> arosales: thanks for doing a review, any bit helps empty the queue is appreciated
[18:57] <arosales> marcoceppi, it is a very rookie review, just touching on the basics
[18:57] <arosales> marcoceppi, but glad to help where I can
[18:59] <arosales> sidnei, +1 for calling your testing for the test sub dir so we can test those in our charm testing automation
=== ociuhandu_ is now known as ociuhandu
=== CyberJacob|Away is now known as CyberJacob
=== hatch_ is now known as hatch
=== gary_poster is now known as gary_poster|away
[22:21] <InformatiQ> does every web app needs in metadata: "provides: website"?"
=== CyberJacob is now known as CyberJacob|Away
[22:47] <marcoceppi> InformatiQ: it's not a requirement, but we highly suggest it
[23:16] <InformatiQ> marcoceppi: marcoceppi but then i get "I: relation website has no hooks"
[23:38] <marcoceppi> InformatiQ: you should have some relation hookos
[23:51] <_bjorne> someone now why im alwas get this answer in apache logfile: /MAAS/metadata//2012-03-01/user-data HTTP/1.1" 404 200 "-" "Python-urllib/2.7" on the second and so on.. the first node is function not the others.