Install hook error due to modprobe 8021q failure
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Dimiter Naydenov |
Bug Description
On local provider, deployment of a charm can fail with an error similar to:
machine-1: 2014-08-06 09:19:28 ERROR juju.worker runner.go:219 exited "networker": command "lsmod | grep -q 8021q || modprobe 8021q" failed (code: 1, stdout: , stderr: modprobe: ERROR: ../libkmod/
or:
machine-1: 2014-08-05 21:27:06 ERROR juju.worker runner.go:219 exited "networker": command "lsmod | grep -q 8021q || modprobe 8021q" failed (code: 1, stdout: , stderr: FATAL: Could not load /lib/modules/
modprobe in the lxc container is using the host path to attempt to load the module. This appears to be a symptom of the module not being loaded in the host.
After the install fails due to the uniter exiting (or "something") something fixes the problem as a "juju resolved --retry" almost always succeeds.
Logs attached.
tags: | added: ci |
Changed in juju-core: | |
assignee: | nobody → Dimiter Naydenov (dimitern) |
status: | Triaged → Won't Fix |
status: | Won't Fix → In Progress |
tags: |
added: network removed: networker |
Changed in juju-core: | |
milestone: | next-stable → 1.21-alpha1 |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
Note that "modprobe 8021q" on the host before starting the container should be a workaround.