Problem after upgrade from 3.9.1-1 to 3.9.1-7 (relation "storageadmin_pincard" does)

[Manfred_Wilhelm]

Brief description of the problem

After update to the new Version 3.9.9.1-7 i got this error when i’am trying to access a share via <Shares → [Share]>

Detailed step by step instructions to reproduce the problem

goto Storage/Shares and click on a Share-Name

Web-UI screenshot

Error Traceback provided on the Web-UI

        Traceback (most recent call last):

File “/opt/rockstor/src/rockstor/rest_framework_custom/generic_view.py”, line 41, in _handle_exception
yield
File “/opt/rockstor/src/rockstor/storageadmin/views/user.py”, line 113, in get_queryset
return combined_users()
File “/opt/rockstor/src/rockstor/storageadmin/views/ug_helpers.py”, line 69, in combined_users
temp_uo.pincard_allowed, temp_uo.has_pincard = pincard_states(temp_uo) # noqa E501
File “/opt/rockstor/src/rockstor/system/pinmanager.py”, line 146, in pincard_states
pincard_present = has_pincard(user)
File “/opt/rockstor/src/rockstor/system/pinmanager.py”, line 129, in has_pincard
pins = Pincard.objects.filter(user=int(uid_field)).count()
File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/db/models/query.py”, line 318, in count
return self.query.get_count(using=self.db)
File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/db/models/sql/query.py”, line 466, in get_count
number = obj.get_aggregation(using, [‘__count’])[‘__count’]
File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/db/models/sql/query.py”, line 447, in get_aggregation
result = compiler.execute_sql(SINGLE)
File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/db/models/sql/compiler.py”, line 840, in execute_sql
cursor.execute(sql, params)
File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/db/backends/utils.py”, line 64, in execute
return self.cursor.execute(sql, params)
File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/db/utils.py”, line 98, in exit
six.reraise(dj_exc_type, dj_exc_value, traceback)
File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/db/backends/utils.py”, line 64, in execute
return self.cursor.execute(sql, params)
ProgrammingError: relation “storageadmin_pincard” does not exist
LINE 1: SELECT COUNT(*) AS “__count” FROM “storageadmin_pincard” WHE…
^

[phillxnet (Philip Guyton)]

@Manfred_Wilhelm Welcome to the Rockstor community.

Your report is a little confusing as it points to a failed db migration when non have happened between 3.9.1-1 to 3.9.1-7. Could it be that you mean an upgrade from some version less than 3.8-14.3 to 3.9.1-7 (see later for details). You might find that a reboot will sort this however. If you paste the output of the following command run as root it should indicate what has been applied db migration wise (this will only work on more recent version of Rockstor):

/opt/rockstor/bin/django showmigrations

You may well find that a reboot will sort this as the db migration may sort itself out.

From:

@Manfred_Wilhelm

ProgrammingError: relation “storageadmin_pincard” does not exist

relates to the following addition:

Dev log for 3.8-15

Hello Everyone, Rockstor 3.8-14.03 is now available! Like the previous two updates in this new cycle, this is also a big one. @Flyer has contributed a pincard based password recovery system for users including root(with a bit of extra security). The system is pretty interesting to me and something security conscious users may like a lot! The UI side of it has the signature @Flyer snappy-ness which is pretty cool. I made the samba service independent of rockstor-bootstrap which was giving grief…

If you have in fact upgraded from such an old version (ie < 3.8.15) then if you find that a reboot does not sort your install out then you may want to take a look at the following post as in the mean time we have changed our database migration system; essentially if you were not running a stable subscritpion with auto update enabled you may have to have stopped off at 3.8.15 first.

Upgrading to 3.8.16 from 3.8-14 or before? Read this

This guide is for subscribers to Stable updates. Rockstor upgrade from 3.8.15 to the latest release, 3.8.16 is simple. Just click on the update notification in the UI and be on your way. However, some users tend to be on prior versions and may try to upgrade directly to 3.8.16 and this will most likely break. We sent out an e-mail in advance of releasing 3.8.16 to get your system upgraded to 3.8.15 for a smooth transition. But it’s totally understandable some users couldn’t do that in time. This…

The part that may apply to you is the heading:
“I have a broken system after upgrading to 3.8.16. What do I do?”

Obviously as that post is now quite old it would be better, if you are to take the alternative re-install route describe there, to use the latest iso which as of this post is 3.9.1.iso.

Hope that helps.