Activity log for bug #1895712

Date Who What changed Old value New value Message
2020-09-15 17:05:29 Jeff Hillman bug added bug
2020-09-30 20:26:13 Adam Dyess charm-advanced-routing: status New Incomplete
2020-10-01 03:12:42 Adam Dyess charm-advanced-routing: importance Undecided Low
2020-10-01 03:12:52 Adam Dyess charm-advanced-routing: assignee Adam Dyess (addyess)
2021-07-21 17:53:13 Drew Freiberger charm-advanced-routing: status Incomplete Confirmed
2021-07-21 17:53:17 Drew Freiberger charm-advanced-routing: importance Low High
2021-07-21 17:54:39 Drew Freiberger summary [feature] add charm config to auto apply config action-managed-update=false set in bundle does not apply the configuration during initial deployment
2021-07-21 17:56:59 Drew Freiberger description Currently, by design, the charm only applies the routing config when the apply-changes action is run. This is useful when migrating to advanced-routing from policy-routing, as well as updating changes. On a clean deploy, if one has already tested these settings, the need to run the action is still there. The proposal is to add a charm config settings that says something to the effect of "auto-apply-config" or something like that, so that only a deploy of the charm (by itself or in a bundle), the config would be applied without the need to run the actions. This will also help with Foundation Cloud Engine automation. On a clean deploy, the advanced-routing charm doesn't honor the setting action-managed-update = false. Either config-changed or run-action apply-changes must be run on the units to affect the initial configurations in a bundle.yaml. This is needed for Solutions QA and Foundation Cloud Engine automation.
2022-10-13 04:17:16 Eric Chen tags bseng-482
2022-11-22 12:15:19 Sudeep Bhandari charm-advanced-routing: assignee Adam Dyess (addyess) Sudeep Bhandari (sudeephb)
2022-11-23 04:33:57 Sudeep Bhandari charm-advanced-routing: importance High Low
2022-11-23 09:09:26 Eric Chen charm-advanced-routing: assignee Sudeep Bhandari (sudeephb)