Thanks to forum member rockmar for reporting this 3.8.15-11 issue. It would seem that in addition to the already altered save order to cater for our new django v 1.8.16 strickter behaviour:
there appears to be a related issue in pool.py:
File "/opt/rockstor/src/rockstor/rest_framework_custom/generic_view.py", line 40, in handleexception
File "/opt/rockstor/src/rockstor/storageadmin/views/pool.py", line 268, in post
File "/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/db/models/fields/related.py", line 750, in add
File "/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/db/models/base.py", line 685, in save
"unsaved related object '%s'." % field.name
ValueError: save() prohibited to prevent data loss due to unsaved related object 'pool'.
Please update the following forum thread with this issues resolution:
Having a quick look at this one now.
save pool object as django 1.8 more strict #1551
Akin to an earlier change in disk.py but this time in
With the above added p.save() command/commit a pool was successfully created in an identical scenario that had previously reproduced the original reporters error.
Remove redundant save(). #1551
disk_set.add() in the above line implicitly calls save on pool because it's a
ForeignKey. See https://docs.djangoproject.com/en/1.8/ref/models/relations/#django.db.models.fields.related.RelatedManager.add
Closing as fixed by #1552 :