Property mapping for Metadef properties regressed to "name" from "property"
Bug #1492579 reported by
Lakshmi N Sampath
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Searchlight |
Fix Released
|
High
|
Lakshmi N Sampath |
Bug Description
Property mapping for Metadef properties regressed to "name" from "property".
Glance Metadef plugin at some point in previous commits had a regression on the mapping for property name.
Previous it was "property" and now its changed to "name" which causes the listener to fail on property updates with objects and namespaces.
To recreate the bug. Try updating a property on a namespace and check if the name of the property in the elastic search document which will not have the updated name.
Changed in searchlight: | |
milestone: | none → liberty-rc1 |
assignee: | nobody → Lakshmi N Sampath (lakshmi-sampath) |
importance: | Undecided → High |
Changed in searchlight: | |
status: | Fix Committed → Fix Released |
Changed in searchlight: | |
milestone: | liberty-rc1 → 0.1.0.0 |
To post a comment you must log in.
We could either change property structure to the previous like
}]
or keep it the same and change the listener to process this structure.
'properties': [{
' default' : 'value1',
' description' : None,
' name': 'property1',
' type': 'string',
' title': 'something title'
}]
I have tested the fix with with both structures to work. The old way of calling property name as "property" was done to make it more specific for properties but I could change it either way. Lets discuss it and i can provide the patch.