MySQL charm: hook failed: "config-changed"

[Marco Ceppi]

Hi Daniele,

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.

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.

Thanks,
Marco Ceppi


On Thu, Feb 6, 2014 at 9:23 AM, Daniele Stroppa
<daniele.stroppa at joyent.com>wrote:

> David,
>
> 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.
>
> @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?
>
> Daniele
>
>
> On Wed, Feb 5, 2014 at 8:05 PM, David Cheney <david.cheney at canonical.com>wrote:
>
>> 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.
>>
>>
>> On Thu, Feb 6, 2014 at 3:44 AM, Daniele Stroppa <
>> daniele.stroppa at joyent.com> wrote:
>>
>>> David,
>>>
>>> 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
>>> https://bugs.launchpad.net/juju-core/+bug/1236994 it works fine.
>>>
>>> Daniele
>>>
>>>
>>> On Wed, Feb 5, 2014 at 9:30 AM, David Cheney <david.cheney at canonical.com
>>> > wrote:
>>>
>>>> https://bugs.launchpad.net/juju-core/+bug/1236994 is a dup of
>>>> https://bugs.launchpad.net/juju-core/+bug/1247299, both of which are
>>>> claimed to be resolved.
>>>>
>>>> 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.
>>>>
>>>>
>>>> On Wed, Feb 5, 2014 at 8:25 PM, Jorge O. Castro <jorge at ubuntu.com>wrote:
>>>>
>>>>> On Tue, Feb 4, 2014 at 11:10 PM, David Cheney
>>>>> <david.cheney at canonical.com> wrote:
>>>>> > Looks like an apparmor issue to me.
>>>>>
>>>>> We've had this problem in the past with MySQL/apparmor/local provider:
>>>>>
>>>>> https://bugs.launchpad.net/juju-core/+bug/1236994
>>>>> https://bugs.launchpad.net/juju-core/+bug/1247299
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Jorge Castro
>>>>> Canonical Ltd.
>>>>> http://juju.ubuntu.com/ - Automate your Cloud Infrastructure
>>>>>
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20140206/d3f6d7ad/attachment.html>