cf-charmers team mailing list archive

[Kapil Thangavelu <kapil.thangavelu@xxxxxxxxxxxxx>]

On Fri, Oct 17, 2014 at 1:58 PM, Alexander Lomov <lomov.as@xxxxxxxxx> wrote:

> Hey, Kapil and Cory. Thank you for answers.
>
> Possible issue was in time (or timeout) that was required to build cf
> charms on mavhine-0. Today I've updated juju to version 1.20.9 and left
> deployment for an hour, after that I had deployed CF.
>
> For now I think that possible reason was that CF charm changed place where
> it builds charms for CF components from "cloudoundry" service to machine-0.
>

afaik, trunk doesn't build charms, it consumes them from the public charm
store.


> And the main thing that confused me was that I didn't saw any services
> appeared in `juju status` json after first minutes of deployment. Could it
> be the right reason?
>

you still haven't clarified which provider your using, additionally the
full all-machines.log would be useful to debug.

cheers,

Kapil


>
> Best wishes,
> Alex L.
>
>
>
> On 17 October 2014 16:00, Cory Johns <cory.johns@xxxxxxxxxxxxx> wrote:
>
>> Alex,
>>
>> If the cloudfoundry service is failing to even show up in `juju
>> status` as a service, then this sounds like a provider issue.  I've
>> had times where juju has failed to provision things properly due to
>> intermittent provider issues.  Usually, these show up in the
>> agent-status field under the machines section of juju status and
>> sometimes `juju retry-provisioning <machine number>` can resolve it.
>>
>> As Kapil mentioned, there shouldn't be any issues with deploying the
>> trunk branch of the CF charm.  This sounds like a provider issue,
>> possibly intermittent, and retrying on the same or a different
>> provider should help.
>>
>> On Thu, Oct 16, 2014 at 6:36 PM, Kapil Thangavelu
>> <kapil.thangavelu@xxxxxxxxxxxxx> wrote:
>> > Hi Alexander
>> >
>> > We've done a few deploys on ec2 and baremetal the past week.. Afaik
>> trunk
>> > should be good. I just got off a plane and haven't had a chance to look
>> > through your debug log. One thing that would be helpful and is currently
>> > missing is which provider you were using. Also a tail tends to be after
>> the
>> > fact, there's an option on debug log to replay the whole log.
>> >
>> > Thanks
>> > Kapil
>> >
>> >
>> > On Thursday, October 16, 2014, Alexander Lomov <lomov.as@xxxxxxxxx>
>> wrote:
>> >>
>> >> Hey, all.
>> >>
>> >> Today I was able to try to deploy Cloud Foundry with the juju charm.
>> I've
>> >> updated my juju charm to 139 revision and followed steps described in
>> >> README. The issue is that execution of `cfdeploy` command stucked.
>> After
>> >> trying to run cfdeploy script manually I've found out that execution
>> stops
>> >> on `juju deploy` command. During the time `juju deploy` is stucked,
>> `juju
>> >> status` shows that there waw no any service created (the value for
>> services
>> >> in result yaml is `services: {}`). I've waited for 20-30 minutes and
>> nothing
>> >> changed.
>> >>
>> >> The test was performed on Mac OS with Juju 1.20.7 (the latest from
>> >> homebrew formulas) and on Ubuntu with Juju 1.20.8.
>> >>
>> >> A tail for `juju debug-log` was following:
>> >>
>> https://gist.githubusercontent.com/allomov/eb313ec67fa3666de909/raw/23bf58ffeffecf407cd226f99a10737ba9b2f7dd/fail-for-juju-1.20.7-macos.log
>> >>
>> >> I also tried to deploy the version of Juju charm from this page
>> >> https://manage.jujucharms.com/~cf-charmers/trusty/cloudfoundry, in
>> this case
>> >> machine for cloud foundry charm was created and after this process
>> stopped.
>> >>
>> >> Could you tell what can be wrong with this setup?
>> >>
>> >>
>> >> 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
>> >
>>
>
>