Note that you have to be logged in to see the 'charm-storage' job. Otherwise those links come back as 404.
I'm investigating this now.
John
On Thu, Sep 28, 2017 at 7:50 PM, Burton Swan <email address hidden> wrote:
> ** Description changed: > > - Juju version: 2.3-alpha1 > + Juju version: 2.3-alpha1 and 2.2 series. > > PR7868 is highly likely the cause of this issue: > https://github.com/juju/juju/pull/7868 > > Using charm-storage test as an example: > http://ci.jujucharms.com/job/charm-storage/ > > Re-run the last successful job, revision build 5743, commit a906cf9, > works well: > http://ci.jujucharms.com/job/charm-storage/2027/ > > Then re-run the first failed job, revision build 5745, commit 774f2f0, > failed again: > http://ci.jujucharms.com/job/charm-storage/2028/ > 2017-09-28 14:11:49 ERROR ('0', 'agent is not communicating with the > server', 1149.777357) > > commit 774f2f0 also triggered other failures, e.g.: > http://ci.jujucharms.com/job/multi-series-charm/ > > This issue can also be manually reproduced on the latest Juju 2.3-alpha1 > by run: > $ ./assess_storage.py $ENV $JUJU_BIN $JUJU_DATA > > ** Description changed: > > Juju version: 2.3-alpha1 and 2.2 series. > > PR7868 is highly likely the cause of this issue: > https://github.com/juju/juju/pull/7868 > + > + On Juju 2.2 series it is PR7863: > + https://github.com/juju/juju/pull/7863 > > Using charm-storage test as an example: > http://ci.jujucharms.com/job/charm-storage/ > > Re-run the last successful job, revision build 5743, commit a906cf9, > works well: > http://ci.jujucharms.com/job/charm-storage/2027/ > > Then re-run the first failed job, revision build 5745, commit 774f2f0, > failed again: > http://ci.jujucharms.com/job/charm-storage/2028/ > 2017-09-28 14:11:49 ERROR ('0', 'agent is not communicating with the > server', 1149.777357) > > commit 774f2f0 also triggered other failures, e.g.: > http://ci.jujucharms.com/job/multi-series-charm/ > > This issue can also be manually reproduced on the latest Juju 2.3-alpha1 > by run: > $ ./assess_storage.py $ENV $JUJU_BIN $JUJU_DATA > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1720155 > > Title: > Juju agent is not communicating with the server. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/juju/+bug/1720155/+subscriptions >
Note that you have to be logged in to see the 'charm-storage' job.
Otherwise those links come back as 404.
I'm investigating this now.
John
On Thu, Sep 28, 2017 at 7:50 PM, Burton Swan <email address hidden>
wrote:
> ** Description changed: /github. com/juju/ juju/pull/ 7868 ci.jujucharms. com/job/ charm-storage/ ci.jujucharms. com/job/ charm-storage/ 2027/ ci.jujucharms. com/job/ charm-storage/ 2028/ ci.jujucharms. com/job/ multi-series- charm/ /github. com/juju/ juju/pull/ 7868 /github. com/juju/ juju/pull/ 7863 ci.jujucharms. com/job/ charm-storage/ ci.jujucharms. com/job/ charm-storage/ 2027/ ci.jujucharms. com/job/ charm-storage/ 2028/ ci.jujucharms. com/job/ multi-series- charm/ /bugs.launchpad .net/bugs/ 1720155 /bugs.launchpad .net/juju/ +bug/1720155/ +subscriptions
>
> - Juju version: 2.3-alpha1
> + Juju version: 2.3-alpha1 and 2.2 series.
>
> PR7868 is highly likely the cause of this issue:
> https:/
>
> Using charm-storage test as an example:
> http://
>
> Re-run the last successful job, revision build 5743, commit a906cf9,
> works well:
> http://
>
> Then re-run the first failed job, revision build 5745, commit 774f2f0,
> failed again:
> http://
> 2017-09-28 14:11:49 ERROR ('0', 'agent is not communicating with the
> server', 1149.777357)
>
> commit 774f2f0 also triggered other failures, e.g.:
> http://
>
> This issue can also be manually reproduced on the latest Juju 2.3-alpha1
> by run:
> $ ./assess_storage.py $ENV $JUJU_BIN $JUJU_DATA
>
> ** Description changed:
>
> Juju version: 2.3-alpha1 and 2.2 series.
>
> PR7868 is highly likely the cause of this issue:
> https:/
> +
> + On Juju 2.2 series it is PR7863:
> + https:/
>
> Using charm-storage test as an example:
> http://
>
> Re-run the last successful job, revision build 5743, commit a906cf9,
> works well:
> http://
>
> Then re-run the first failed job, revision build 5745, commit 774f2f0,
> failed again:
> http://
> 2017-09-28 14:11:49 ERROR ('0', 'agent is not communicating with the
> server', 1149.777357)
>
> commit 774f2f0 also triggered other failures, e.g.:
> http://
>
> This issue can also be manually reproduced on the latest Juju 2.3-alpha1
> by run:
> $ ./assess_storage.py $ENV $JUJU_BIN $JUJU_DATA
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Juju agent is not communicating with the server.
>
> To manage notifications about this bug go to:
> https:/
>