[Bug 1050001] Re: API shutdown(timeout=X) call always tries to call stop(), spewing error messages to the console when the container is already stopped

[Serge Hallyn]

@stgraber,

heh, obviously I meant to pull that from the cut-paste :)

** Description changed:

  Title should say it all, example is available at:
  http://paste.ubuntu.com/1201056/
  
  18:45 <hallyn> d'oh.  i think i line got dropped there
  18:46 <hallyn> the if (timeout > 0) should be if (!retv && timeout > 0)
  18:46 <hallyn> we're calling c->stop() on a stopped container otherwise
  
  The test case is:
  
  root at amd1:~/bzr/lxc/lxc# python3
- Python 3.2.3 (default, Sep 10 2012, 12:07:24) 
+ Python 3.2.3 (default, Sep 10 2012, 12:07:24)
  [GCC 4.7.1 20120908 (prerelease)] on linux2
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import lxc
  __main__:1: Warning: The python-lxc API isn't yet stable and may change at any point in the future.
  >>> c=lxc.Container("qlvm3")
  >>> c.start()
  True
- >>> c.stop(timeout=5)
- Traceback (most recent call last):
-   File "<stdin>", line 1, in <module>
- TypeError: stop() takes no keyword arguments
  >>> c.shutdown(timeout=5)
  lxc_container: failed to receive answer for the command
  lxc_container: failed to send command
  True
  >>>

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1050001

Title:
  API shutdown(timeout=X) call always tries to call stop(), spewing
  error messages to the console when the container is already stopped

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1050001/+subscriptions