imagebuild failed installing a package inside base image chroot because /run/lock wasn't available
Bug #1337877 reported by
Ursula Junque
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu CI Engine |
Fix Released
|
High
|
Ursula Junque |
Bug Description
When installing click-dev, that pulled schroot as a dependency and installing that package failed as postinst script couldn't find /var/lock. Further investigation led to realizing /run/lock didn't exist inside the chroot.
We need to investigate what cases we're not covering when creating the bind mounts before chrooting into the image, so this won't happen again.
Related branches
lp:~ursinha/uci-engine/add-run-lock-to-imagebuild-chroot
- PS Jenkins bot (community): Approve (continuous-integration)
- Celso Providelo (community): Approve
-
Diff: 32 lines (+12/-0)1 file modifiedimage-builder/imagebuilder/cloud_image.py (+12/-0)
Changed in uci-engine: | |
importance: | Undecided → High |
status: | New → Triaged |
milestone: | none → uce-1 |
Changed in uci-engine: | |
status: | Triaged → In Progress |
Changed in uci-engine: | |
status: | In Progress → Fix Committed |
assignee: | nobody → Ursula Junque (ursinha) |
To post a comment you must log in.
plars suggested we try adding '/run/lock' to the bind mount list, I have a deployment and am testing his patch.