juju doesn't check if 8021q module is present before modprobing it
Bug #1316762 reported by
Tycho Andersen
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Fix Released
|
High
|
Dimiter Naydenov | ||
Bug Description
It would be nice if juju (>= 1.19) checked if the 8021q module was present before modprobing it; this prevents juju from bootstrapping in a container, where it could if the host had the module but juju can't actually modprobe.
Related branches
lp:~dimitern/juju-core/435-lp-1316762-conditional-modprobe-8021q
- Juju Engineering: Pending requested
-
Diff: 28 lines (+4/-3)2 files modifiedprovider/maas/environ.go (+3/-2)
provider/maas/environ_test.go (+1/-1)
| tags: | added: cloud-installer |
| Changed in juju-core: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| milestone: | none → 2.0 |
| tags: | added: local-provider lxc |
| Changed in juju-core: | |
| milestone: | 2.0 → 1.20.0 |
Revision history for this message
| Dimiter Naydenov (dimitern) wrote | #1 |
| Changed in juju-core: | |
| status: | Triaged → In Progress |
| assignee: | nobody → Dimiter Naydenov (dimitern) |
| Changed in juju-core: | |
| status: | In Progress → Fix Committed |
| Changed in juju-core: | |
| milestone: | 1.20.0 → 1.19.2 |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
I'm adding a check with "lsmod | grep -q 8021q" to verify if 8021q is loaded already, and not try to modprobe it. It should work both inside a normal machine and in a lxc container.