<div dir="ltr">Hi Daniele,<div><br></div><div>That's expected behavior with Amulet, as it caches the charm locally to do some verification against the charms in the deployment. So it deploys from local: rather than the charm store.</div>
<div><br></div><div>As for the dataset-size, if 80% isn't a sane value, I'll try various other default values to make sure it deploys consistently and everytime on all cloud providers. I'm in the process of writing tests for the MySQL charm so we'll have better exposure of this issue sooner.</div>
<div><br></div><div>Thanks,<br>Marco Ceppi</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Feb 6, 2014 at 9:23 AM, Daniele Stroppa <span dir="ltr"><<a href="mailto:daniele.stroppa@joyent.com" target="_blank">daniele.stroppa@joyent.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">David,<div><br></div><div>I missed that requirements, I was using the 3.5 kernel. I've updated to the raring kernel, and deploying mysql using 'juju deploy' with no additional configuration still give the same issue. Setting the innodb_buffer_pool_size as mentioned yesterday works fine. </div>
<div><br></div><div>@Marco: One thing I've noticed is that when deploying mysql with juju deploy the charm being deployed is 'cs:precise/mysql-33', while when running the test the charm is 'local:precise/mysql-310' (in the .py file I do specify 'd.add('mysql', charm='cs:precise/mysql-33')'). Is this normal?</div>
<span class="HOEnZb"><font color="#888888">
<div><br></div><div>Daniele</div></font></span><div><div class="h5">
<div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Feb 5, 2014 at 8:05 PM, David Cheney <span dir="ltr"><<a href="mailto:david.cheney@canonical.com" target="_blank">david.cheney@canonical.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">You said earlier that you were using the local provider. Have you applied the raring kernel update to this machine ? This is required if you want to use LXC on Precise.</div>
<div><div><div class="gmail_extra"><br><br>
<div class="gmail_quote">On Thu, Feb 6, 2014 at 3:44 AM, Daniele Stroppa <span dir="ltr"><<a href="mailto:daniele.stroppa@joyent.com" target="_blank">daniele.stroppa@joyent.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">David,<div><br></div><div>I'm using juju 1.16.4.1 on Ubuntu 12.04. If I just deploy mysql with no config changes, the issue still exists. However, if I decrease the size of the innodb_buffer_pool_size setting (using "juju set mysql dataset-size='512M'") as stated in <a href="https://bugs.launchpad.net/juju-core/+bug/1236994" target="_blank">https://bugs.launchpad.net/juju-core/+bug/1236994</a> it works fine.</div>
<span><font color="#888888">
<div><br></div><div>Daniele</div></font></span></div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Feb 5, 2014 at 9:30 AM, David Cheney <span dir="ltr"><<a href="mailto:david.cheney@canonical.com" target="_blank">david.cheney@canonical.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><a href="https://bugs.launchpad.net/juju-core/+bug/1236994" target="_blank">https://bugs.launchpad.net/juju-core/+bug/1236994</a> is a dup of <a href="https://bugs.launchpad.net/juju-core/+bug/1247299" target="_blank">https://bugs.launchpad.net/juju-core/+bug/1247299</a>, both of which are claimed to be resolved.<div>
<br></div><div>Daniele, if this is still a problem with the latest development release of Juju please reopen one of these or open a new issue as soon as possible.</div></div><div><div><div class="gmail_extra">
<br><br><div class="gmail_quote">
On Wed, Feb 5, 2014 at 8:25 PM, Jorge O. Castro <span dir="ltr"><<a href="mailto:jorge@ubuntu.com" target="_blank">jorge@ubuntu.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On Tue, Feb 4, 2014 at 11:10 PM, David Cheney<br>
<<a href="mailto:david.cheney@canonical.com" target="_blank">david.cheney@canonical.com</a>> wrote:<br>
> Looks like an apparmor issue to me.<br>
<br>
</div>We've had this problem in the past with MySQL/apparmor/local provider:<br>
<br>
<a href="https://bugs.launchpad.net/juju-core/+bug/1236994" target="_blank">https://bugs.launchpad.net/juju-core/+bug/1236994</a><br>
<a href="https://bugs.launchpad.net/juju-core/+bug/1247299" target="_blank">https://bugs.launchpad.net/juju-core/+bug/1247299</a><br>
<span><font color="#888888"><br>
<br>
<br>
--<br>
Jorge Castro<br>
Canonical Ltd.<br>
<a href="http://juju.ubuntu.com/" target="_blank">http://juju.ubuntu.com/</a> - Automate your Cloud Infrastructure<br>
</font></span></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div></div></div></div>
</blockquote></div><br></div>