Public bug reported:
Error reporting for container issues is pretty much non-existent.
Issues such as why an LXC won't start is not being reported. Some of
this is due to the LXC Python API not providing any sort of error
reporting (see bug #1542438).
However, we should be better than we are now in error reporting.
** Affects: libertine
Importance: Medium
Status: Triaged
** Affects: libertine/devel
Importance: Medium
Status: Triaged
** Affects: libertine/trunk
Importance: Medium
Status: Triaged
** Affects: libertine (Ubuntu)
Importance: Medium
Status: Triaged
** Also affects: libertine/devel
Importance: Undecided
Status: New
** Also affects: libertine/trunk
Importance: Undecided
Status: New
** Also affects: libertine (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libertine/devel
Status: New => Triaged
** Changed in: libertine/trunk
Status: New => Triaged
** Changed in: libertine (Ubuntu)
Status: New => Triaged
** Changed in: libertine/devel
Importance: Undecided => Medium
** Changed in: libertine/trunk
Importance: Undecided => Medium
** Changed in: libertine (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1562139
Title:
Need better error reporting for container issues
To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1562139/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
