nova boot failed when use the chinese metadata key and value

Bug #1737711 reported by shuangyang.qian
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Invalid
Wishlist
huanhongda

Bug Description

I get the wrong msg like bellow:

Invalid input for field/attribute metadata. Value: {u'\\u4e2d\\u6587\\u5143\\u6570\\u636e': u'\u963f\u65af\u987f\u53d1\u751f'}. Additional properties are not allowed (u'\\u4e2d\\u6587\\u5143\\u6570\\u636e' was unexpected) (HTTP 400) (Request-ID: req-3e9ea1d0-8384-41e9-8b00-36e6740262e4)

I think it't better to support the chinese key.

Revision history for this message
shuangyang.qian (shuangyang.qian) wrote :

anyone who notice this bug or defect? may be i describe this problem not very clearly.

when boot VM with Chinese metadata, it failed with the error that invalid input. I think we should fix this to support Chinese metadata key.

Changed in nova:
assignee: nobody → shuangyang.qian (shuangyang.qian)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

Fix proposed to branch: master
Review: https://review.openstack.org/536236

Changed in nova:
status: New → In Progress
Changed in nova:
assignee: shuangyang.qian (shuangyang.qian) → wanghongtao (hongtao.wang)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Fix proposed to branch: master
Review: https://review.openstack.org/571352

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on nova (master)

Change abandoned by wanghongtao (<email address hidden>) on branch: master
Review: https://review.openstack.org/571352
Reason: work on original so abandon this patch

Revision history for this message
Eric Fried (efried) wrote :

Hello. A few of us discussed this in IRC today [1]. Can you please provide more specifics about what's driving this? Is it a need or a want? What specific use case(s) are you trying to address?

Thanks!

[1] http://eavesdrop.openstack.org/irclogs/%23openstack-nova/%23openstack-nova.2018-06-01.log.html#t2018-06-01T15:07:28

Changed in nova:
status: In Progress → Incomplete
Revision history for this message
wanghongtao (hongtao.wang) wrote :

@Eric Fried
Hello ,I'm very sorry,i didn't take part in it in time discussed in IRC.I want to solve metadata key support chinese.

Revision history for this message
Eric Fried (efried) wrote :

Right, we understand *what* you're trying to do. We'd like to know *why*.

Changed in nova:
status: Incomplete → In Progress
Eric Fried (efried)
Changed in nova:
status: In Progress → Incomplete
Changed in nova:
assignee: wanghongtao (hongtao.wang) → huanhongda (hongda)
status: Incomplete → In Progress
Revision history for this message
Eric Fried (efried) wrote :

Still need to understand the motivation for this.

Changed in nova:
status: In Progress → Incomplete
Revision history for this message
huanhongda (hongda) wrote :

@Eric Fried
Some customers in China need to set metadata's key in Chinese. So that they can do some customized operations using Chinese.
For flavor extra specs, there's no need to support unicode for key so far.

Changed in nova:
status: Incomplete → In Progress
Revision history for this message
Eric Fried (efried) wrote :

More core team discussion [1] concluded that, if we're going to do this, it's going to need a blueprint/spec and most likely a microversion. If you wish to pursue it, you may register a blueprint here [2] and submit a spec to the nova-specs repository. More information on this process can be found at [3].

Thanks!

[1] http://eavesdrop.openstack.org/irclogs/%23openstack-nova/%23openstack-nova.2018-07-30.log.html#t2018-07-30T18:32:33
[2] https://blueprints.launchpad.net/nova/+addspec
[3] https://docs.openstack.org/nova/latest/contributor/blueprints.html

Changed in nova:
importance: Undecided → Wishlist
status: In Progress → Invalid
Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Change abandoned by Balazs Gibizer (<email address hidden>) on branch: master
Review: https://review.opendev.org/536236
Reason: This patch is stale with negative review and the referred bug is in Invalid state. If you wish to continue working on this then please follow the instructions in the last comment of the bug report.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.