In a distributed async system there is no guarantee that it will ever be
processed in a timely manner. Especially if an agent is down.
I don't think adding a --wait option to changing config is reasonable.
On Wed, Mar 11, 2020 at 4:21 AM Marian Gasparovic <
<email address hidden>> wrote:
> Well, because we had to bypass another race condition in glance-
> simplestreams-sync we set it to run:false. Then waited till juju was
> settled and set run to true. So at this stage juju is stable and it
> would continue immediately before gsss downloads files
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: Juju bugs
> https://bugs.launchpad.net/bugs/1866171
>
> Title:
> [feature request] juju config --wait
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1866171/+subscriptions
>
In a distributed async system there is no guarantee that it will ever be
processed in a timely manner. Especially if an agent is down.
I don't think adding a --wait option to changing config is reasonable.
On Wed, Mar 11, 2020 at 4:21 AM Marian Gasparovic <
<email address hidden>> wrote:
> Well, because we had to bypass another race condition in glance- /bugs.launchpad .net/bugs/ 1866171 /bugs.launchpad .net/juju/ +bug/1866171/ +subscriptions
> simplestreams-sync we set it to run:false. Then waited till juju was
> settled and set run to true. So at this stage juju is stable and it
> would continue immediately before gsss downloads files
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: Juju bugs
> https:/
>
> Title:
> [feature request] juju config --wait
>
> To manage notifications about this bug go to:
> https:/
>