fix the docs, not the code, As discussion in the nova-api meeting [1]. That's why I'm setting the status to "invalid".
[1] http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-03-08-12.00.log.html ** Changed in: nova Status: In Progress => Invalid ** Changed in: nova Assignee: kevin shen (kevin.shen) => (unassigned) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1550671 Title: The limit of injected file conetent length is incorrect Status in OpenStack Compute (nova): Invalid Bug description: According to http://developer.openstack.org/api-ref-compute-v2.1.html#createServer , the perameter personality has limits about path length and content length. And it is pointed out that the content should be base64 encoded string and the content length limit is the limit of base64 decoded raw data, not the base64 encoded data. But in the current implementation: https://github.com/openstack/nova/blob/master/nova/compute/api.py#L266-L277 we are checking the base64 encoded data. That is, for example, the quota limit for content length is 256, and user provided a file with the length of 256, exception.OnsetFileContentLimitExceeded error will rasie as after base64 encoding, the file length will grow. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1550671/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
