Can you include g-api logs showing why the request was rejected?
https://docs.openstack.org/api-ref/image/v2/index.html?expanded=update-image-detail
I can't see a way for n-cpu to provide the store name even if it could work that out as g-api specifically asks for the following when updating the locations associated with an image:
{ [..] 'locations': [ 'uri': { 'metadata': { 'key': 'value', [..] } }, ] }
This smells like a config issue and/or bug in g-api is causing it to reject a valid request from n-cpu.
Can you include g-api logs showing why the request was rejected?
https:/ /docs.openstack .org/api- ref/image/ v2/index. html?expanded= update- image-detail
I can't see a way for n-cpu to provide the store name even if it could work that out as g-api specifically asks for the following when updating the locations associated with an image:
{
[..]
'locations': [
'uri': {
'metadata': {
'key': 'value',
[..]
}
},
]
}
This smells like a config issue and/or bug in g-api is causing it to reject a valid request from n-cpu.