what they want to do.
<menn0> wwitzel3: sounds good
<wwitzel3> menn0: and then what ever they tell me to do, I'll do :)
<wwitzel3> menn0: we could always go with the olde, "local provider isn't production"
<menn0> wwitzel3: true
<wwitzel3> menn0: but that isn't very friendl ;)
<menn0> wwitzel3: no it's not and deleting the templates probably isn't that hard
<menn0> wwitzel3: although I guess it's not an upgrade problem actually
<menn0> wwitzel3: this happens even with a fresh bootstrap
<menn0> wwitzel3: I wonder if there's a way that Juju could detect that the certs are bad
<wwitzel3> menn0: maybe, I don't know enough about how that template is generated .. I think we won't that the machine-0 certs are bad until another machine attempts to connect.
<menn0> waigani: since thumper doesn't appear to be around could you have a look at http://reviews.vapour.ws/r/284/ please?
<waigani> menn0: half way through
<menn0> waigani: ok cheers :)
<wwitzel3> menn0: ec2 is good
<menn0> wwitzel3: my bootstrap just finished here and I still see the problem
<menn0> wwitzel3: :(
<menn0> wwitzel3: the template was definitely re-created from scratch. I watched Juju do that by monitoring lxc-ls --fancy
<davecheney> perrito666: https://golang.org/doc/faq#closures_and_goroutines
<perrito666> davecheney: tx
<davecheney> talks about a different problem, but the underlying cause is the same
<davecheney> for _, x := range A_SLICE_OF_VALUES {
<davecheney>         go something(x)
<davecheney> }
<davecheney> in this case it was
<davecheney> for _, x := range A_SLICE_OF_VALUES {
<davecheney> append(something, &x)
<wwitzel3> menn0: hrmm, i've got nothing .. all clean http://paste.ubuntu.com/8738740/ (machine-0), http://paste.ubuntu.com/8738764/ (unit-mysql)
<perrito666> davecheney: that is why it does x:=x to get a non shared x I assume
<wwitzel3> menn0: all-machines is aggregating .. machine-1 and machine-2 are good .. not even one occurance of that error you are seeing :/
<menn0> wwitzel3: well I'm seeing the same as what I reported on the tick