On Thu, Feb 5, 2015 at 2:56 AM, Dimiter Naydenov
dimiter.nayde...@canonical.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
However, the networker even in 1.21 is only causing issues when
modifying /etc/network/interfaces inappropriately it *does not* decide
what addresses a
Thanks lots, Sam!!
This is all very, very helpful advice.
Best Regards,
Ken
On 5 February 2015 at 14:59, Samuel Cozannet samuel.cozan...@canonical.com
wrote:
Hey Ken,
My advice if you fall into an error state with a bundle like this is to
deploy it charm by charm (or use the deployment
Hey Ken,
My advice if you fall into an error state with a bundle like this is to
deploy it charm by charm (or use the deployment script provided), as those
may manage race conditions between the charms.
Let me explain this a little more what we call a race condition.
When deploying complex
Hi all,
I'm currently using the 'data-analytics-with-sql-like' bundle.
Sometimes it works fine but sometimes it deploys with an error
and I don't know how to fix it without doing 'destroy-environment' and
deploy again (which takes time).
The error (in 'juju stat') is,
Hello Juju!
There is a new bug fix release of charm-tools which fixes issues with those
running charm proof in CI/build/testing environments. It is strongly
suggested those running charm-proof in any automated fashion update to this
latest release. To verify which version of charm-tools you are
On 05/02/15 20:56, Dimiter Naydenov wrote:
Hey Tim,
I'm sorry the networker is causing trouble for you guys. It was
causing issues for us in MaaS and EC2 as well, there were several
fixes to reduce the networker's impact and in fact it is now totally
disabled on trunk. It will stay that way
Hey, I have been backporting licencing fixes into utils, syslog and testing
for 1.21 release. While doing this I noticed that the revs testing and
utils used in 1.21 are quite far from what we use in master so, in order to
prevent bringing unwanted changes to 1.21 by bumping the deps to HEAD I
