openvswitch-switch isn't installed if netplan schema defines an ovs bridge
Bug #1891608 reported by
Björn Tillenius
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| curtin |
Fix Committed
|
Undecided
|
Ryan Harper | ||
| curtin (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| Xenial |
New
|
Undecided
|
Unassigned | ||
| Bionic |
New
|
Undecided
|
Unassigned | ||
| Focal |
New
|
Undecided
|
Unassigned | ||
| Groovy |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
If the network config defines an openvswitch bridge, curtin doesn't install the openvswitch-switch package, which is needed. For examle, a schema like this:
network:
version: 2
bridges:
br-empty:
Looking at the current code in curtin, it only handles the case where's there's a top-level 'openvswitch' section, or the renderer is 'openvswitch' (which was the previous proposal for openvswitch support in netplan)
Related branches
~raharper/curtin:fix/netplan-ovs-package-install
- Server Team CI bot: Approve (continuous-integration)
- Paride Legovini: Approve
-
Diff: 87 lines (+10/-37)3 files modifiedcurtin/net/deps.py (+4/-1)
examples/tests/network_v2_ovs.yaml (+3/-32)
tests/unittests/test_curthooks.py (+3/-4)
| Changed in curtin: | |
| assignee: | nobody → Ryan Harper (raharper) |
| status: | Confirmed → In Progress |
To post a comment you must log in.

Yeah, the implementation changed after curtin landed this.