OSAPI: 500 error on bad server personality contents

[Alex Meade]

The error trace and command can be found here:

http://paste.openstack.org/show/1953/

This occurred because the base64 encoded contents are jibbersish (invalid file contents), perhaps the error message should state this.

[Alex Meade (alex-meade)]

NOTE: This is still a valid bug as of rev: 1532, Sept. 8, 2011.

[Brian Waldon (bcwaldon)]

So this bug is caused by an exception thrown from rpc cast/call when we try to send a unicode character as part of our parameters. We might be able to solve this with some robustness in to_primitive.

[Davanum Srinivas (DIMS) (dims-v)]

With latest code, we are getting the following in the logs

2012-10-23 17:05:37 INFO nova.api.openstack.wsgi [req-5fb7ce4b-e321-46ff-8b6a-761831f6286a admin admin] POST http://192.168.1.110:8774/v2/e7d865e4c2c5497aa5a1ba9f2e861d90/servers
2012-10-23 17:05:37 INFO nova.api.openstack.wsgi [req-5fb7ce4b-e321-46ff-8b6a-761831f6286a admin admin] HTTP exception thrown: Personality content for /etc/banner.txt cannot be decoded
2012-10-23 17:05:37 INFO nova.api.openstack.wsgi [req-5fb7ce4b-e321-46ff-8b6a-761831f6286a admin admin] http://192.168.1.110:8774/v2/e7d865e4c2c5497aa5a1ba9f2e861d90/servers returned with HTTP 400
2012-10-23 17:05:37 INFO nova.osapi_compute.wsgi.server [req-5fb7ce4b-e321-46ff-8b6a-761831f6286a admin admin] 192.168.1.110 - - [23/Oct/2012 17:05:37] "POST /v2/e7d865e4c2c5497aa5a1ba9f2e861d90/servers HTTP/1.1" 400 359 0.047406

And the HTTP/XML response is very clear as well

< HTTP/1.1 400 Bad Request
< Content-Length: 163
< Content-Type: application/xml; charset=UTF-8
< X-Compute-Request-Id: req-5fb7ce4b-e321-46ff-8b6a-761831f6286a
< Date: Tue, 23 Oct 2012 21:05:37 GMT
* HTTP error before end of send, stop sending
<
* Closing connection #0
<badRequest code="400" xmlns="http://docs.openstack.org/compute/api/v1.1"><message>Personality content for /etc/banner.txt cannot be decoded</message></badRequest>