Merge ~rmalz/charm-advanced-routing:rmalz/modify_networkd_conf into charm-advanced-routing:master
Status: | Merged |
---|---|
Approved by: | Eric Chen |
Approved revision: | 20c53a26e87b460f7b033ff77f8e7df790d6f159 |
Merged at revision: | 28162e0fb93b07f3894b00ad40d2093c12bbe234 |
Proposed branch: | ~rmalz/charm-advanced-routing:rmalz/modify_networkd_conf |
Merge into: | charm-advanced-routing:master |
Diff against target: |
102 lines (+34/-1) 3 files modified
src/lib/advanced_routing_helper.py (+20/-0) src/tests/unit/test_AdvancedRoutingHelper.py (+12/-1) src/tests/unit/test_actions.py (+2/-0) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Robert Gildein | Approve | ||
Andrea Ieri | Approve | ||
🤖 prod-jenkaas-bootstack (community) | continuous-integration | Approve | |
BootStack Reviewers | Pending | ||
Review via email: mp+453785@code.launchpad.net |
Commit message
configure networkd during setup
Systemd in some scenarios can remove any rules defined outside
To fix that ManageForeignRo
Set networkd configuration during charm setup to make rules persistant.
Close LP #2034029
Description of the change
Currently advanced-routing charm assumes that networkd-dispatcher will always trigger /etc/networkd-
networkd-dispatcher awaits for a operational state routable to execute above script, however systemd will not trigger such signal if all interfaces are configured with static ip addresses.
To reproduce problem configure all interfaces in unit to not use dhcp settings.
If at least one interface is configured with dhcp, systemd will generate signal for it and routable.d will be called, thus reproduction will not happen.
Once configured reload networkd service or perform networkctl reload
After changes in systemd [1], any foreign rules will be removed. To workaround this following config has been added [2]
This behavior has been confirmed with https:/
1- https:/
2- https:/
This merge proposal is being monitored by mergebot. Change the status to Approved to merge.