cf-charmers team mailing list archive
-
cf-charmers team
-
Mailing list archive
-
Message #00490
Re: Working deployment
Fix pushed.
On Wed, Aug 13, 2014 at 3:57 PM, Cory Johns <cory.johns@xxxxxxxxxxxxx> wrote:
> Sorry for the delay in the response; we had some overlap in people
> being out recently.
>
> It looks like that error is caused by not setting the admin_secret
> value in the config. It should be more gracefully handled, but if you
> follow the instructions in the README.md for generating the config.yml
> file prior to deploying the charm, you can work around it.
>
> I will push a fix for handling it more gracefully in a few minutes.
>
> On Fri, Aug 8, 2014 at 2:08 AM, <prismakov@xxxxxxxxx> wrote:
>> Hi guys,
>>
>> Ubuntu 14.04.1 LTS
>> local juju environment
>> cloudfoundry charm rev 115
>>
>> cloudfoundry:
>> charm: local:trusty/cloudfoundry-0
>> exposed: false
>> units:
>> cloudfoundry/0:
>> agent-state: error
>> agent-state-info: 'hook failed: "config-changed"'
>> agent-version: 1.20.1.1
>> machine: "1"
>> public-address: 10.0.3.226
>>
>>
>>
>> 2014-08-08 05:50:10 INFO config-changed Traceback (most recent call last):
>> 2014-08-08 05:50:10 INFO config-changed File
>> "/var/lib/juju/agents/unit-cloudfoundry-0/charm/hooks/config-changed", line
>> 145, in <module> 2014-08-08 05:50:10 INFO config-changed manage() 2014-08-08
>> 05:50:10 INFO config-changed File
>> "/var/lib/juju/agents/unit-cloudfoundry-0/charm/hooks/config-changed", line
>> 139, in manage 2014-08-08 05:50:10 INFO config-changed manager.manage()
>> 2014-08-08 05:50:10 INFO config-changed File
>> "/var/lib/juju/agents/unit-cloudfoundry-0/charm/hooks/charmhelpers/core/services.py",
>> line 113, in manage 2014-08-08 05:50:10 INFO config-changed
>> self.provide_data() 2014-08-08 05:50:10 INFO config-changed File
>> "/var/lib/juju/agents/unit-cloudfoundry-0/charm/hooks/charmhelpers/core/services.py",
>> line 119, in provide_data 2014-08-08 05:50:10 INFO config-changed data =
>> provider.provide_data() 2014-08-08 05:50:10 INFO config-changed File
>> "/var/lib/juju/agents/unit-cloudfoundry-0/charm/hooks/cloudfoundry/contexts.py",
>> line 383, in provide_data 2014-08-08 05:50:10 INFO config-changed 'domain':
>> self.get_domain(), 2014-08-08 05:50:10 INFO config-changed File
>> "/var/lib/juju/agents/unit-cloudfoundry-0/charm/hooks/cloudfoundry/contexts.py",
>> line 351, in get_domain 2014-08-08 05:50:10 INFO config-changed env =
>> APIEnvironment(creds['api_address'], creds['api_password']) 2014-08-08
>> 05:50:10 INFO config-changed KeyError: 'api_address' 2014-08-08 05:50:11
>> ERROR juju.worker.uniter uniter.go:486 hook failed: exit status 1
>>
>> - Alex P.
>>
>>
>> On Aug 7, 2014, at 20:28, Alexander Lomov <lomov.as@xxxxxxxxx> wrote:
>>
>> Hi, Ben.
>>
>> I like the way cloudfoundry charm is deployed now. Working with
>> bosh-template is good idea.
>>
>> Unfortunately I wasn't able to deploy it yesterday using standard
>> instructions from README file. For the first sight the reason is in the
>> router, router process isn't started. Today will try with updated charm.
>>
>> Best wishes,
>> Alex L.
>>
>>
>>
>> On 1 August 2014 03:30, Benjamin Saller <benjamin.saller@xxxxxxxxxxxxx>
>> wrote:
>>>
>>> Barring some minor issues we have a recent (!73) deployment working in
>>> that we've been able to deploy some basic apps.
>>>
>>> This is a big milestone for us. Thanks to the team and thanks to Jim and
>>> company for helping us to resolve a couple of facepalm issues stemming from
>>> differences in the trusty cloud image and stem cells (very minor but hard to
>>> identify).
>>>
>>> We still have an open issue with cgroups memory quota application which
>>> we've patched around for the time being, and will work towards a long lived
>>> fix in the near term.
>>>
>>> We will also record and publish the costs/difficulty of adding support for
>>> 175/176 cf-releases, we don't expect any real issues there as the current
>>> codebase is designed around handling this type of change.
>>>
>>> I'll be in Germany representing the Canonical teams work to some of our
>>> internal stakeholders next week but we expect to be able to push things
>>> forward faster now that we have a working base.
>>>
>>> Thanks,
>>> Ben
>>>
>>> --
>>> 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
>>>
>>
>> --
>> 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
>>
>>
>>
>> --
>> 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