action-managed-update=false set in bundle does not apply the configuration during initial deployment
Bug #1895712 reported by
Jeff Hillman
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
charm-advanced-routing |
Confirmed
|
Low
|
Unassigned |
Bug Description
On a clean deploy, the advanced-routing charm doesn't honor the setting action-
This is needed for Solutions QA and Foundation Cloud Engine automation.
Changed in charm-advanced-routing: | |
importance: | Undecided → Low |
assignee: | nobody → Adam Dyess (addyess) |
tags: | added: bseng-482 |
Changed in charm-advanced-routing: | |
assignee: | Adam Dyess (addyess) → Sudeep Bhandari (sudeephb) |
Changed in charm-advanced-routing: | |
importance: | High → Low |
Changed in charm-advanced-routing: | |
assignee: | Sudeep Bhandari (sudeephb) → nobody |
To post a comment you must log in.
there is a config option that provides this feature:
juju config advanced-routing action- managed- update= false