also to be clear the clock skew involves not only the server machines, but
also the juju client machine which generates the cert. I'd suggest giving
1.21 a per curtis's suggestion as it may have a fix for this.
On Thu, Nov 13, 2014 at 7:51 AM, Curtis Hovey <email address hidden> wrote:
> Can you test 1.21-beta1 or beta2 when it is released. the cert issues
> were fixes a few weeks ago in the 1.21 version.
>
> If the network issue is still present, please provide the logs from one of
> the units/machines the charm was deployed to. You can ssh into the machine
> and get these logs
> /var/log/cloud-init-output.log
> /var/log/juju/machine*.log
>
> --
> You received this bug notification because you are subscribed to juju-
> core.
> https://bugs.launchpad.net/bugs/1376906
>
> Title:
> arm* agents cannot call home, but amd64 can
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1376906/+subscriptions
>
also to be clear the clock skew involves not only the server machines, but
also the juju client machine which generates the cert. I'd suggest giving
1.21 a per curtis's suggestion as it may have a fix for this.
On Thu, Nov 13, 2014 at 7:51 AM, Curtis Hovey <email address hidden> wrote:
> Can you test 1.21-beta1 or beta2 when it is released. the cert issues cloud-init- output. log juju/machine* .log /bugs.launchpad .net/bugs/ 1376906 /bugs.launchpad .net/juju- core/+bug/ 1376906/ +subscriptions
> were fixes a few weeks ago in the 1.21 version.
>
> If the network issue is still present, please provide the logs from one of
> the units/machines the charm was deployed to. You can ssh into the machine
> and get these logs
> /var/log/
> /var/log/
>
> --
> You received this bug notification because you are subscribed to juju-
> core.
> https:/
>
> Title:
> arm* agents cannot call home, but amd64 can
>
> To manage notifications about this bug go to:
> https:/
>