metadata update fails if preferered is null as the database schema doesn't allows null value
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Released
|
Undecided
|
David Hill |
Bug Description
metadata update fails if preferered is null as the database schema doesn't allows null value and here is a patch to fix in in sqlalchemy.
[root@lab-
--- api.py.orig 2017-07-11 13:47:55.591859922 -0400
+++ api.py 2017-07-11 14:15:32.904711884 -0400
@@ -2546,6 +2546,8 @@
# that will not take effect using one session and we will rewrite,
# in that case, single record - first one added with this call.
session = get_session()
+ if not meta_value:
+ meta_value = 'none'
item = {"value": meta_value, "updated_at": timeutils.utcnow()}
meta_ref = _export_
Changed in manila: | |
milestone: | none → pike-3 |
Also, this is reproducable if we're not using clustering admin credentials to interface with the netapp appliance.