| 2018-06-11 03:17:21 |
zhongjun |
description |
It is same bug such as nova in grizzly.
So in grizzly nova, It is already modified.
becuase of this, "manila metadata function" not working in below situation.
1. manila metadata $(share_id) set Hadoop_TAG_1.2.2=samsung_service
2. manila metadata $(share_id) unset Hadoop_TAG_1.2.2
=> error!! ERROR: Metadata item was not found (HTTP 404)
So It must be modified.
By default, routes.mapper.Mapper.resource adds a bunch of formatted
routes that accept anything after a '.'. Our spec says only .xml
and .json are accepted so limit the formatting to those valuse.
This allows identifiers with a '.' in urls. A few tests were added
to the extensions test to prove that .xml and .json are stripped
but other values are not. |
It is same bug such as cinder.
So in cinder, It is already modified.
link: https://bugs.launchpad.net/cinder/+bug/1307956
becuase of this, "manila metadata function" not working in below situation.
1. manila metadata $(share_id) set Hadoop_TAG_1.2.2=samsung_service
2. manila metadata $(share_id) unset Hadoop_TAG_1.2.2
=> error!! ERROR: Metadata item was not found (HTTP 404)
So It must be modified.
By default, routes.mapper.Mapper.resource adds a bunch of formatted
routes that accept anything after a '.'. Our spec says only .xml
and .json are accepted so limit the formatting to those valuse.
This allows identifiers with a '.' in urls. A few tests were added
to the extensions test to prove that .xml and .json are stripped
but other values are not. |
|
