libertine-container-manager crashes when log file not found

Bug #1596661 reported by Larry Price
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Libertine
Status tracked in Devel
Devel
Fix Released
Medium
Christopher Townsend
Trunk
Fix Released
Medium
Christopher Townsend
libertine (Ubuntu)
Fix Released
Medium
Christopher Townsend

Bug Description

If I have a "corrupt" container in my ContainersConfig.json, I only see a stack trace when I run any command requiring the container to start because the lxc log file cannot be found. Because of the exception, the ContainersConfig.json is not reverted on error.

Example ContainersConfig.json: https://paste.ubuntu.com/17986067/

Command with output: https://paste.ubuntu.com/17986092/

We should do a try-catch in the dump function and print out a generic error message such as "Unable to start container."

Similar to #1596020.

Related branches

Changed in libertine (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Libertine CI Bot (libertine-ci-bot) wrote :

Fix committed into lp:libertine at revision 261, scheduled for release in libertine, milestone Unknown

Changed in libertine:
status: In Progress → Fix Committed
Changed in libertine (Ubuntu):
status: Triaged → In Progress
assignee: nobody → Christopher Townsend (townsend)
Changed in libertine (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.