I'm not convinced that metadata munging is appropriate.
Also, you are only allowed to move bugs from New -> Confirmed if you
aren't the bug originator. Confirmed means a second person has confirmed
it.
** Changed in: nova
Status: Confirmed => Opinion
** Changed in: nova
Importance: Undecided => Low
--
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/1117326
Title:
server metadata accepts leading and trailing whitespaces in key and
value pairs
Status in OpenStack Compute (Nova):
Opinion
Bug description:
While doing a set(PUT) and update (POST) operation in server metadata
it accepts leading and trailing white space in key and value pairs .
Set Request :
URI:
http://10.2.3.169:8774/v2/5a88678e1b9a4c1d9c44ccbaad108bdc/servers
/069a060b-691f-445e-ae80-f7f6bf4d4b48/metadata
{
"metadata": {
"key1 ":" value1 ",
" key2": " value2 "
}
}
response : Status : 200 (OK)
{
"metadata": {
" key2": " value2 ",
"key1 ": " value1 "
}
}
Ideally white spaces should not be allowed and should be trimmed
before set and update request.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1117326/+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
