I do believe we prune old action data in newer releases of Juju. I'd have
to ask Eric to know what the trigger is for pruning old actions. Its also
possible there is just a bug in the pruning logic.
On Fri, Nov 3, 2017 at 7:40 PM, Matt Dirba <email address hidden> wrote:
> I have tried this with both a default bootstrap of the juju controller,
> as well as a bootstrap of a controller with the following config values.
>
> automatically-retry-hooks: false
> enable-os-refresh-update: false
> enable-os-upgrade: false
> firewall-mode: none
> test-mode: true
> transmit-vendor-metrics: false
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1729880
>
> Title:
> juju 2.2.4 and 2.2.6 actions dissappear when state is changed from
> running to complete
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1729880/+subscriptions
>
I do believe we prune old action data in newer releases of Juju. I'd have
to ask Eric to know what the trigger is for pruning old actions. Its also
possible there is just a bug in the pruning logic.
On Fri, Nov 3, 2017 at 7:40 PM, Matt Dirba <email address hidden> wrote:
> I have tried this with both a default bootstrap of the juju controller, retry-hooks: false os-refresh- update: false vendor- metrics: false /bugs.launchpad .net/bugs/ 1729880 /bugs.launchpad .net/juju/ +bug/1729880/ +subscriptions
> as well as a bootstrap of a controller with the following config values.
>
> automatically-
> enable-
> enable-os-upgrade: false
> firewall-mode: none
> test-mode: true
> transmit-
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https:/
>
> Title:
> juju 2.2.4 and 2.2.6 actions dissappear when state is changed from
> running to complete
>
> To manage notifications about this bug go to:
> https:/
>