← Back to team overview

cf-charmers team mailing list archive

Re: CF charm failed on 'config-changed' hook.

 

Are you planning to add any kind of version freezing to prevent such
situations ?

Thank you,
Alex L.


On 4 September 2014 18:27, Alexander Lomov <lomov.as@xxxxxxxxx> wrote:

> Cool. Hope it will fix the issue.
>
>
> On 4 September 2014 18:25, Benjamin Saller <benjamin.saller@xxxxxxxxxxxxx>
> wrote:
>
>> I believe this is due to Kapil changing the etcd charms interfaces (a
>> move he notified us about). We'll have to go in and change our context
>> class for etcd.
>>
>> -Ben
>>
>>
>> On Thu, Sep 4, 2014 at 8:22 AM, Alexander Lomov <lomov.as@xxxxxxxxx>
>> wrote:
>>
>>> Hey, everyone.
>>>
>>> After successful deployment to AWS I retried to deploy CF juju charm
>>> again and deployment failed on 'config-changed' hook. (take in account that
>>> I've updated my cf.yml file)
>>>
>>> Here is a log of cloudfoudry unit:
>>> https://gist.githubusercontent.com/allomov/188131c84fdbcbab5ea8/raw/1b3070c9b3cf5faa719594df8e095f50923ea99b/fail.log
>>>
>>> Juju agent-version - 1.20.6
>>> Juju version - 1.20.6-trusty-amd64
>>> cloudfoundry charm revno 144
>>>
>>> It seems that it failed after it deployment of all charms it generated
>>> (I have 16 charms in `juju status` list, all with "running" status except
>>> cloudfoundry charm). Anyway I can't log in through CF cli.
>>>
>>> Could anyone say the reason it could happen ?
>>>
>>>
>>> Thank you,
>>> Alex L.
>>>
>>> --
>>> Mailing list: https://launchpad.net/~cf-charmers
>>> Post to     : cf-charmers@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~cf-charmers
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>

Follow ups

References