Re: [Bug 1542438] [NEW] Python LXC api needs to be much better at error reporting

2016-02-07 Thread Serge Hallyn
Hi, the intent is that you can set the logfile and loglevel and find out more about how it failed for those. While there is talk about work to improve on the startup failure debugging, it is still based on the logfile output. As an example: ^C2 ✗ serge@sl ~ $ python3 Python 3.4.3+ (default,

Re: [Bug 1542438] [NEW] Python LXC api needs to be much better at error reporting

2016-02-07 Thread Serge Hallyn
Hi, the intent is that you can set the logfile and loglevel and find out more about how it failed for those. While there is talk about work to improve on the startup failure debugging, it is still based on the logfile output. As an example: ^C2 ✗ serge@sl ~ $ python3 Python 3.4.3+ (default,

[Bug 1542438] [NEW] Python LXC api needs to be much better at error reporting

2016-02-05 Thread Christopher Townsend
Public bug reported: I use the Python API extensively on the lp:libertine project. However, when there is an error somewhere in the LXC layer, the only thing that is returned is False which is not very useful when trying to figure out what has gone wrong. For example, I try to use the

[Bug 1542438] [NEW] Python LXC api needs to be much better at error reporting

2016-02-05 Thread Christopher Townsend
Public bug reported: I use the Python API extensively on the lp:libertine project. However, when there is an error somewhere in the LXC layer, the only thing that is returned is False which is not very useful when trying to figure out what has gone wrong. For example, I try to use the