Cannot resolve keyword 'group' into field after upgrade from V4.2.7 to V4.3.3

[mackermann-psi]

Error Message and Config

<class 'django.core.exceptions.FieldError'>

Cannot resolve keyword 'group' into field. Choices are: address, assignments, bookmarks, comments, created, custom_field_data, description, email, groups, id, journal_entries, last_updated, link, name, phone, subscriptions, tagged_items, tags, title

Python version: 3.11.2
NetBox version: 4.3.3
Plugins: 
  netbox_documents: 0.7.3
  netbox_ipcalculator: 1.4.11
  netbox_qrcode: 0.0.18
  netbox_topology_views: 4.3.0

I made a copy of the Database in psql via "
create database netbox_43 with template netbox;
All owner rights in the database set to my netbox user,
After then i made a complete new installation in an other directory with V4.3.3
running upgrade.sh and all seems to bee good.

After i went to sites

and klick on button Contacts I got the error message you see above.

Any help would be appreciated. Thanks

[markkuleinio]

then i made a complete new installation in an other directory with V4.3.3

Just guessing that you have now an incorrect reference somewhere, you have to be really careful if you are running/having two NetBox instances on the same server in parallel.

I have never duplicated a psql database with that "create database with template" command so I cannot comment on that.

[mackermann-psi]

First thanks for your fast reply.

You are right. It is carfull having more netbox instances on one server. you have to deal with different redis and unicorn ports.

I mad a complete new installation without any external plugins and follow strictly the Netbox documentation.
Testing with "python3 manage.py runserver 0.0.0.0:8000 --insecure"
And it runs with an empty database.

Also i follow the guide "Replicating Netbox" and made a backup and restore.
then I run upgrade.sh an test it again with "python3 manage.py runserver 0.0.0.0:8000 --insecure"

Now I get the same error as before.
At which corner do i have to look. It seams to be a database problem?!

Regards
Michael

[markkuleinio]

Yet another guess based on this: #18902, how about deleting all your table preferences?

[mackermann-psi]

Again, Thank you also for the Link!

This statemant solve my problem
UPDATE public.users_userconfig SET "data"='{}'::jsonb;

Regards