cf-charmers team mailing list archive

[Cory Johns <cory.johns@xxxxxxxxxxxxx>]

It looks to me like your Juju environment didn't successfully
bootstrap.  (That error is due to `juju api-endpoints` failing.)

Perhaps try manually bootstrapping and making sure that `juju status`
looks ok (with just machine-0) before running cfdeploy?

On Fri, Jan 16, 2015 at 8:27 AM, Alex Prysmakou
<aliaksandr.prysmakou@xxxxxxxxxxx> wrote:
> Thank you Cory for the help.
>
> But I still have issues.
> See attached files please.
> I tried also to deploy using fresh vagrant box:
>
> ➜  cloudfoundry  ./cfdeploy -l c1oudc0w
> (sudo) installing python-virtualenv package.
> Setting up virutalenv.
> Installing CF CLI (this requires sudo access)
> Waiting for State Server |......                          | 20.0% 0:05:56
> Traceback (most recent call last):
>   File "./cfdeploy", line 194, in <module>
>     main()
>   File "./cfdeploy", line 113, in wrapper
>     f(*args, **kwargs)
>   File "./cfdeploy", line 166, in main
>     until(juju_state_server, bar=bar, message="Waiting for State Server")
>   File "/home/vagrant/trusty/cloudfoundry/cloudfoundry/utils.py", line 330,
> in until
>     return wait_for(0, 20, *callbacks, **kwargs)
>   File "/home/vagrant/trusty/cloudfoundry/cloudfoundry/utils.py", line 320,
> in wait_for
>     result = callback()
>   File "/home/vagrant/trusty/cloudfoundry/cloudfoundry/utils.py", line 353,
> in juju_state_server
>     endpoints = sh.juju('api-endpoints', '--format=json').json
>   File "/home/vagrant/trusty/cloudfoundry/cloudfoundry/utils.py", line 197,
> in json
>     return json.loads(self.stdout)
>   File "/usr/lib/python2.7/json/__init__.py", line 338, in loads
>     return _default_decoder.decode(s)
>   File "/usr/lib/python2.7/json/decoder.py", line 366, in decode
>     obj, end = self.raw_decode(s, idx=_w(s, 0).end())
>   File "/usr/lib/python2.7/json/decoder.py", line 384, in raw_decode
>     raise ValueError("No JSON object could be decoded")
> ValueError: No JSON object could be decoded
>
> Any thoughts?
>
>
> -Alex Prysmakou
>
> On 1/16/15 00:47, Cory Johns wrote:
>
> Just confirmed that with the updates pushed, it deploys fine now.
> Again, apologies for it being in a broken state.
>
> On Thu, Jan 15, 2015 at 2:55 PM, Cory Johns <cory.johns@xxxxxxxxxxxxx>
> wrote:
>
> Alex,
>
> Sorry for the delay.  It seems that the individual charm updates to
> support release 190 were not pushed up to the store.  I've pushed them
> now, which should hopefully fix it, and am running a test on my end to
> confirm.
>
> On Thu, Jan 15, 2015 at 1:39 PM, Alex Prysmakou
> <aliaksandr.prysmakou@xxxxxxxxxxx> wrote:
>
> Hi Cory,
>
> Thank you for the answer.
> I've attached logfiles.
> My env: Trusty on PC, 16GB RAM, juju 1.20.14
>
> - Alex P.
>
> On 1/13/15 22:34, Cory Johns wrote:
>
> Alex,
>
> I'm not aware of any reason why it would fail to deploy, and it
> remember it working the last time I deployed it, though that was some
> time ago.
>
> Can you provide more details on how it failed?  I will attempt to
> deploy it when I have some time, but I'm not sure if that will be
> today or early tomorrow.
>
> On Tue, Jan 13, 2015 at 3:52 AM, Aliaksandr Prysmakou
> <aliaksandr.prysmakou@xxxxxxxxxxx> wrote:
>
> Hi Cory,
>
> I'm trying to deploy CF using juju charms (local provider) without
> success.
> Could you please provide information about charms revision that 100%
> works.
> Do I need to use Juju from development branch?
>
> - Alex Prysmakou / Altoros
>
> --
> Alex Prysmakou / Altoros
> Skype: prysmakou
> www.altoros.com | blog.altoros.com | twitter.com/altoros
>
>
> --
> Alex Prysmakou / Altoros
> Skype: prysmakou
> www.altoros.com | blog.altoros.com | twitter.com/altoros