Subscribed field-high. I think it'd be reasonable to expect the charm to support config changes, or at least to block when they aren't (e.g. changing ovs-use-veth).
For the record, a manual workaround is available: simply remove the old bond with ovs-vsctl del-port br-data <the old bond>
Subscribed field-high. I think it'd be reasonable to expect the charm to support config changes, or at least to block when they aren't (e.g. changing ovs-use-veth).
For the record, a manual workaround is available: simply remove the old bond with ovs-vsctl del-port br-data <the old bond>