Create operations can fail silently about pylxd

[stgraber]

You indeed are passing it invalid input :)

alias set to ubuntu/xenial/amd64 should do the trick, or pass 16.04 but then set protocol to simplestreams and server to https://cloud-images.ubuntu.com/releases

[candlerb]

I get the same "Whoops" response with this config too:

config = {
  'source': {
    'alias': '16.04', 'type': 'image', 'mode': 'pull', 'protocol': 'simplestreams', 'server': 'https://cloud-images.ubuntu.com/releases'},
  'name': CONTAINER_NAME,
  'profiles': ['default']
}

But in any case, would you agree that the REST API should return an error for bad parameters, and that pylxd should return the error to the client, probably as an exception?

[stgraber]

Yeah, pylxd should definitely do a better job at catching errors here

[candlerb]

Just for the record, this config does work:

config = {
  'source': {
    'alias': 'ubuntu/xenial/amd64', 'type': 'image', 'mode': 'pull', 'protocol': 'lxd', 'server': 'https://images.linuxcontainers.org'},
  'name': CONTAINER_NAME,
  'profiles': ['default']
}

It creates a container (in stopped state)

[jpic]

Should pylxd raise an exception if it gets a response with a status code > 400 ?

[candlerb]

I think it should

However I already added that patch, so I believe this is different issue.

Here the job submission is accepted, pylxd polls for completion, but pylxd is apparently ignoring the result of the job.

[jpic]

Raising an exception with status code >= 400 will inhibit specific error handling ie. in Container.get - integration tests caught it.

However, raising a RuntimeError on status_code >= 500 works well, adding it to my PR then.

[rockstar]

This is using the deprecated API (though forwarded to the public API for backwards compatibility), which was deprecated for this very reason. If you have similar issues (and by the looks of #77, you do) with the newer API, please report those issues.