Problem after upgrading to 2.3

f...@23media.de

unread,

Feb 27, 2018, 2:41:27 AM2/27/18

to NetBox

Hello,

after upgrading to version 2.3 we have the problem that there is no devices or racks chown on the frontend. If we are clicking on edit device this error appears:

A database programming error was detected while processing this request. Common causes include the following:
Database migrations missing - When upgrading to a new NetBox release, the upgrade script must be run to apply any new database migrations. You can run migrations manually by executing python3 manage.py migrate from the command line.
Unsupported PostgreSQL version - Ensure that PostgreSQL version 9.4 or higher is in use. You can check this by connecting to the database using NetBox's credentials and issuing a query for SELECT VERSION().
The complete exception is provided below:

<class 'django.db.utils.ProgrammingError'>

column dcim_device.virtual_chassis_id does not exist
LINE 1: ...ce"."primary_ip6_id", "dcim_device"."cluster_id", "dcim_devi...
                                                             ^

The upgrade was successfully without errors. We are running with PostgreSQL 9.6 and python 3.

Thanks in advanced.

Florian

Brian Candler

unread,

Feb 27, 2018, 7:48:25 AM2/27/18

to NetBox

Looks like migrations were not applied (no column dcim_device.virtual_chassis_id)

Did you run "./upgrade.sh" ?

f...@23media.de

unread,

Feb 27, 2018, 7:53:46 AM2/27/18

to NetBox

Hi Brian,

I did the ./upgrade.sh and the python3 manage.py migrate but nothing helped.

Cleaning up stale Python bytecode (find . -name "*.pyc" -delete)...
Removing old Python packages (pip3 uninstall -r old_requirements.txt -y)...
Cannot uninstall requirement psycopg2, not installed
Updating required Python packages (pip3 install -r requirements.txt --upgrade)...
Requirement already up-to-date: Django<2.0,>=1.11 in /usr/lib/python3.4/site-packages (from -r requirements.txt (line 1))
Requirement already up-to-date: django-cors-headers>=2.1.0 in /usr/lib/python3.4/site-packages (from -r requirements.txt (line 2))
Requirement already up-to-date: django-debug-toolbar>=1.9.0 in /usr/lib/python3.4/site-packages (from -r requirements.txt (line 3))
Requirement already up-to-date: django-filter>=1.1.0 in /usr/lib/python3.4/site-packages (from -r requirements.txt (line 4))
Requirement already up-to-date: django-mptt>=0.9.0 in /usr/lib/python3.4/site-packages (from -r requirements.txt (line 5))
Requirement already up-to-date: django-rest-swagger>=2.1.0 in /usr/lib/python3.4/site-packages (from -r requirements.txt (line 6))
Requirement already up-to-date: django-tables2>=1.19.0 in /usr/lib/python3.4/site-packages (from -r requirements.txt (line 7))
Requirement already up-to-date: django-timezone-field>=2.0 in /usr/lib/python3.4/site-packages (from -r requirements.txt (line 8))
Requirement already up-to-date: djangorestframework>=3.7.7 in /usr/lib/python3.4/site-packages (from -r requirements.txt (line 9))
Requirement already up-to-date: graphviz>=0.8.2 in /usr/lib/python3.4/site-packages (from -r requirements.txt (line 10))
Requirement already up-to-date: Markdown>=2.6.11 in /usr/lib/python3.4/site-packages (from -r requirements.txt (line 11))
Requirement already up-to-date: natsort>=5.2.0 in /usr/lib/python3.4/site-packages (from -r requirements.txt (line 12))
Requirement already up-to-date: ncclient==0.5.3 in /usr/lib/python3.4/site-packages (from -r requirements.txt (line 13))
Requirement already up-to-date: netaddr==0.7.18 in /usr/lib/python3.4/site-packages (from -r requirements.txt (line 14))
Requirement already up-to-date: paramiko>=2.4.0 in /usr/lib/python3.4/site-packages (from -r requirements.txt (line 15))
Requirement already up-to-date: Pillow>=5.0.0 in /usr/lib64/python3.4/site-packages (from -r requirements.txt (line 16))
Requirement already up-to-date: psycopg2-binary>=2.7.4 in /usr/lib64/python3.4/site-packages (from -r requirements.txt (line 17))
Requirement already up-to-date: py-gfm>=0.1.3 in /usr/lib/python3.4/site-packages (from -r requirements.txt (line 18))
Requirement already up-to-date: pycryptodome>=3.4.11 in /usr/lib64/python3.4/site-packages (from -r requirements.txt (line 19))
Requirement already up-to-date: xmltodict>=0.11.0 in /usr/lib/python3.4/site-packages (from -r requirements.txt (line 20))
Requirement already up-to-date: pytz in /usr/lib/python3.4/site-packages (from Django<2.0,>=1.11->-r requirements.txt (line 1))
Requirement already up-to-date: sqlparse>=0.2.0 in /usr/lib/python3.4/site-packages (from django-debug-toolbar>=1.9.0->-r requirements.txt (line 3))
Requirement already up-to-date: django-js-asset in /usr/lib/python3.4/site-packages (from django-mptt>=0.9.0->-r requirements.txt (line 5))
Requirement already up-to-date: coreapi>=2.3.0 in /usr/lib/python3.4/site-packages (from django-rest-swagger>=2.1.0->-r requirements.txt (line 6))
Requirement already up-to-date: openapi-codec>=1.3.1 in /usr/lib/python3.4/site-packages (from django-rest-swagger>=2.1.0->-r requirements.txt (line 6))
Requirement already up-to-date: simplejson in /usr/lib64/python3.4/site-packages (from django-rest-swagger>=2.1.0->-r requirements.txt (line 6))
Requirement already up-to-date: setuptools>0.6 in /usr/lib/python3.4/site-packages (from ncclient==0.5.3->-r requirements.txt (line 13))
Requirement already up-to-date: lxml>=3.3.0 in /usr/lib64/python3.4/site-packages (from ncclient==0.5.3->-r requirements.txt (line 13))
Requirement already up-to-date: six in /usr/lib/python3.4/site-packages (from ncclient==0.5.3->-r requirements.txt (line 13))
Requirement already up-to-date: cryptography>=1.5 in /usr/lib64/python3.4/site-packages (from paramiko>=2.4.0->-r requirements.txt (line 15))
Requirement already up-to-date: pynacl>=1.0.1 in /usr/lib64/python3.4/site-packages (from paramiko>=2.4.0->-r requirements.txt (line 15))
Requirement already up-to-date: pyasn1>=0.1.7 in /usr/lib/python3.4/site-packages (from paramiko>=2.4.0->-r requirements.txt (line 15))
Requirement already up-to-date: bcrypt>=3.1.3 in /usr/lib64/python3.4/site-packages (from paramiko>=2.4.0->-r requirements.txt (line 15))
Requirement already up-to-date: coreschema in /usr/lib/python3.4/site-packages (from coreapi>=2.3.0->django-rest-swagger>=2.1.0->-r requirements.txt (line 6))
Requirement already up-to-date: uritemplate in /usr/lib/python3.4/site-packages (from coreapi>=2.3.0->django-rest-swagger>=2.1.0->-r requirements.txt (line 6))
Requirement already up-to-date: itypes in /usr/lib/python3.4/site-packages (from coreapi>=2.3.0->django-rest-swagger>=2.1.0->-r requirements.txt (line 6))
Requirement already up-to-date: requests in /usr/lib/python3.4/site-packages (from coreapi>=2.3.0->django-rest-swagger>=2.1.0->-r requirements.txt (line 6))
Requirement already up-to-date: cffi>=1.7; platform_python_implementation != "PyPy" in /usr/lib64/python3.4/site-packages (from cryptography>=1.5->paramiko>=2.4.0->-r requirements.txt (line 15))
Requirement already up-to-date: idna>=2.1 in /usr/lib/python3.4/site-packages (from cryptography>=1.5->paramiko>=2.4.0->-r requirements.txt (line 15))
Requirement already up-to-date: asn1crypto>=0.21.0 in /usr/lib/python3.4/site-packages (from cryptography>=1.5->paramiko>=2.4.0->-r requirements.txt (line 15))
Requirement already up-to-date: jinja2 in /usr/lib64/python3.4/site-packages (from coreschema->coreapi>=2.3.0->django-rest-swagger>=2.1.0->-r requirements.txt (line 6))
Requirement already up-to-date: certifi>=2017.4.17 in /usr/lib/python3.4/site-packages (from requests->coreapi>=2.3.0->django-rest-swagger>=2.1.0->-r requirements.txt (line 6))
Requirement already up-to-date: urllib3<1.23,>=1.21.1 in /usr/lib/python3.4/site-packages (from requests->coreapi>=2.3.0->django-rest-swagger>=2.1.0->-r requirements.txt (line 6))
Requirement already up-to-date: chardet<3.1.0,>=3.0.2 in /usr/lib/python3.4/site-packages (from requests->coreapi>=2.3.0->django-rest-swagger>=2.1.0->-r requirements.txt (line 6))
Requirement already up-to-date: pycparser in /usr/lib/python3.4/site-packages (from cffi>=1.7; platform_python_implementation != "PyPy"->cryptography>=1.5->paramiko>=2.4.0->-r requirements.txt (line 15))
Requirement already up-to-date: MarkupSafe>=0.23 in /usr/lib64/python3.4/site-packages (from jinja2->coreschema->coreapi>=2.3.0->django-rest-swagger>=2.1.0->-r requirements.txt (line 6))
Applying database migrations (python3 netbox/manage.py migrate)...
Operations to perform:
  Apply all migrations: admin, auth, circuits, contenttypes, dcim, extras, ipam, secrets, sessions, tenancy, users, virtualization
Running migrations:
  No migrations to apply.
Collecting static files (python3 netbox/manage.py collectstatic --no-input)...

Simen Linderud

unread,

Feb 27, 2018, 8:53:13 AM2/27/18

to NetBox

Hey,

We experience exactly the same issue.

Done everything according to the documentation.

- Simen

Simon Lindermann

unread,

Feb 27, 2018, 9:19:10 AM2/27/18

to NetBox

Same here but it has been all good after restarting Netbox:

supervisorctl restart netbox

f...@23media.de

unread,

Feb 27, 2018, 9:21:39 AM2/27/18

to NetBox

Restarted the service multiple times but without help

Jeremy Stretch

unread,

Feb 27, 2018, 9:24:13 AM2/27/18

to f...@23media.de, NetBox

From what previous NetBox release are you upgrading? What does `manage.py showmigrations` output?

Jeremy

--
You received this message because you are subscribed to the Google Groups "NetBox" group.
To unsubscribe from this group and stop receiving emails from it, send an email to netbox-discuss+unsubscribe@googlegroups.com.
To post to this group, send email to netbox-discuss@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/netbox-discuss/584c1fbb-3ab9-445b-9547-97ed7e8eed6e%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Simen Linderud

unread,

Feb 27, 2018, 9:30:17 AM2/27/18

to NetBox

Upgraded from 2.2.9.

Output from manage.py is in this pastebin:

https://pastebin.com/XxcnAYzR

- Simen

On Tuesday, February 27, 2018 at 3:24:13 PM UTC+1, Jeremy Stretch wrote:

From what previous NetBox release are you upgrading? What does `manage.py showmigrations` output?

Jeremy

On Tue, Feb 27, 2018 at 9:21 AM, fb via NetBox <netbox-...@googlegroups.com> wrote:

Restarted the service multiple times but without help

Am Dienstag, 27. Februar 2018 15:19:10 UTC+1 schrieb Simon Lindermann:
Same here but it has been all good after restarting Netbox:

supervisorctl restart netbox

Am Dienstag, 27. Februar 2018 14:53:13 UTC+1 schrieb Simen Linderud:
Hey,

We experience exactly the same issue.
Done everything according to the documentation.

- Simen

--
You received this message because you are subscribed to the Google Groups "NetBox" group.

To unsubscribe from this group and stop receiving emails from it, send an email to netbox-discus...@googlegroups.com.
To post to this group, send email to netbox-...@googlegroups.com.

f...@23media.de

unread,

Feb 27, 2018, 9:30:50 AM2/27/18

to NetBox

Hi Jemery,

upgraded from 2.2.9

admin
 [X] 0001_initial
 [X] 0002_logentry_remove_auto_add
auth
 [X] 0001_initial
 [X] 0002_alter_permission_name_max_length
 [X] 0003_alter_user_email_max_length
 [X] 0004_alter_user_username_opts
 [X] 0005_alter_user_last_login_null
 [X] 0006_require_contenttypes_0002
 [X] 0007_alter_validators_add_error_messages
 [X] 0008_alter_user_username_max_length
circuits
 [X] 0001_initial
 [X] 0002_auto_20160622_1821
 [X] 0003_provider_32bit_asn_support
 [X] 0004_circuit_add_tenant
 [X] 0005_circuit_add_upstream_speed
 [X] 0006_terminations
 [X] 0007_circuit_add_description
 [X] 0008_circuittermination_interface_protect_on_delete
 [X] 0009_unicode_literals
 [X] 0010_circuit_status
contenttypes
 [X] 0001_initial
 [X] 0002_remove_content_type_name
dcim
 [X] 0001_initial
 [X] 0002_auto_20160622_1821
 [X] 0003_auto_20160628_1721
 [X] 0004_auto_20160701_2049
 [X] 0005_auto_20160706_1722
 [X] 0006_add_device_primary_ip4_ip6
 [X] 0007_device_copy_primary_ip
 [X] 0008_device_remove_primary_ip
 [X] 0009_site_32bit_asn_support
 [X] 0010_devicebay_installed_device_set_null
 [X] 0011_devicetype_part_number
 [X] 0012_site_rack_device_add_tenant
 [X] 0013_add_interface_form_factors
 [X] 0014_rack_add_type_width
 [X] 0015_rack_add_u_height_validator
 [X] 0016_module_add_manufacturer
 [X] 0017_rack_add_role
 [X] 0018_device_add_asset_tag
 [X] 0019_new_iface_form_factors
 [X] 0020_rack_desc_units
 [X] 0021_add_ff_flexstack
 [X] 0022_color_names_to_rgb
 [X] 0023_devicetype_comments
 [X] 0024_site_add_contact_fields
 [X] 0025_devicetype_add_interface_ordering
 [X] 0026_add_rack_reservations
 [X] 0027_device_add_site
 [X] 0028_device_copy_rack_to_site
 [X] 0029_allow_rackless_devices
 [X] 0030_interface_add_lag
 [X] 0031_regions
 [X] 0032_device_increase_name_length
 [X] 0033_rackreservation_rack_editable
 [X] 0034_rename_module_to_inventoryitem
 [X] 0035_device_expand_status_choices
 [X] 0036_add_ff_juniper_vcp
 [X] 0037_unicode_literals
 [X] 0038_wireless_interfaces
 [X] 0039_interface_add_enabled_mtu
 [X] 0040_inventoryitem_add_asset_tag_description
 [X] 0041_napalm_integration
 [X] 0042_interface_ff_10ge_cx4
 [X] 0043_device_component_name_lengths
 [X] 0044_virtualization
 [X] 0045_devicerole_vm_role
 [X] 0046_rack_lengthen_facility_id
 [X] 0047_more_100ge_form_factors
 [X] 0048_rack_serial
 [X] 0049_rackreservation_change_user
 [X] 0050_interface_vlan_tagging
 [X] 0051_rackreservation_tenant
 [X] 0052_virtual_chassis
 [X] 0053_platform_manufacturer
 [X] 0054_site_status_timezone_description
 [X] 0055_virtualchassis_ordering
extras
 [X] 0001_initial
 [X] 0002_custom_fields
 [X] 0003_exporttemplate_add_description
 [X] 0004_topologymap_change_comma_to_semicolon
 [X] 0005_useraction_add_bulk_create
 [X] 0006_add_imageattachments
 [X] 0007_unicode_literals
 [X] 0008_reports
 [X] 0009_topologymap_type
 [X] 0010_customfield_filter_logic
ipam
 [X] 0001_initial
 [X] 0002_vrf_add_enforce_unique
 [X] 0003_ipam_add_vlangroups
 [X] 0004_ipam_vlangroup_uniqueness
 [X] 0005_auto_20160725_1842
 [X] 0006_vrf_vlan_add_tenant
 [X] 0007_prefix_ipaddress_add_tenant
 [X] 0008_prefix_change_order
 [X] 0009_ipaddress_add_status
 [X] 0010_ipaddress_help_texts
 [X] 0011_rir_add_is_private
 [X] 0012_services
 [X] 0013_prefix_add_is_pool
 [X] 0014_ipaddress_status_add_deprecated
 [X] 0015_global_vlans
 [X] 0016_unicode_literals
 [X] 0017_ipaddress_roles
 [X] 0018_remove_service_uniqueness_constraint
 [X] 0019_virtualization
 [X] 0020_ipaddress_add_role_carp
 [X] 0021_vrf_ordering
secrets
 [X] 0001_initial
 [X] 0002_userkey_add_session_key
 [X] 0003_unicode_literals
sessions
 [X] 0001_initial
tenancy
 [X] 0001_initial
 [X] 0002_tenant_group_optional
 [X] 0003_unicode_literals
users
 [X] 0001_api_tokens
 [X] 0002_unicode_literals
virtualization
 [X] 0001_virtualization
 [X] 0002_virtualmachine_add_status
 [X] 0003_cluster_add_site
 [X] 0004_virtualmachine_add_role

Am Dienstag, 27. Februar 2018 15:24:13 UTC+1 schrieb Jeremy Stretch:

From what previous NetBox release are you upgrading? What does `manage.py showmigrations` output?

Jeremy

On Tue, Feb 27, 2018 at 9:21 AM, fb via NetBox <netbox-...@googlegroups.com> wrote:

Restarted the service multiple times but without help

Am Dienstag, 27. Februar 2018 15:19:10 UTC+1 schrieb Simon Lindermann:
Same here but it has been all good after restarting Netbox:

supervisorctl restart netbox

Am Dienstag, 27. Februar 2018 14:53:13 UTC+1 schrieb Simen Linderud:
Hey,

We experience exactly the same issue.
Done everything according to the documentation.

- Simen

--
You received this message because you are subscribed to the Google Groups "NetBox" group.

To unsubscribe from this group and stop receiving emails from it, send an email to netbox-discus...@googlegroups.com.
To post to this group, send email to netbox-...@googlegroups.com.

Jeremy Stretch

unread,

Feb 27, 2018, 9:58:22 AM2/27/18

to f...@23media.de, NetBox

I just installed v2.2.9 on a new instance, switched to the master branch (v2.3.0), and ran upgrade.sh. Everything appears to have worked as expected. All of the migrations were run:

Running migrations:
Applying circuits.0010_circuit_status... OK
Applying dcim.0050_interface_vlan_tagging... OK
Applying dcim.0051_rackreservation_tenant... OK
Applying dcim.0052_virtual_chassis... OK
Applying dcim.0053_platform_manufacturer... OK
Applying dcim.0054_site_status_timezone_description... OK
Applying dcim.0055_virtualchassis_ordering... OK
Applying extras.0009_topologymap_type... OK
Applying extras.0010_customfield_filter_logic... OK
Applying ipam.0021_vrf_ordering... OK

Is it possible you had experimented with a previous v2.3 beta release using the same database? If so, the database may falsely indicate that migrations have already been applied.

To unsubscribe from this group and stop receiving emails from it, send an email to netbox-discuss+unsubscribe@googlegroups.com.
To post to this group, send email to netbox-discuss@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/netbox-discuss/7743430c-b0e5-47bf-b0ab-ea7cb4c42491%40googlegroups.com.

f...@23media.de

unread,

Feb 27, 2018, 10:17:32 AM2/27/18

to NetBox

Hi Jeremy,

yes we tried the 2.3-beta with the same database, its possible to fix this problem?

Jeremy Stretch

unread,

Feb 27, 2018, 10:32:13 AM2/27/18

to f...@23media.de, NetBox

Hmm, it should be. First, of course, make a backup of the current database:

pg_dump netbox > /var/tmp/netbox.sql

Let's try marking the migrations from v2.3.0 as not applied. Do this:

python3 manage.py migrate circuits 0009 --fake
python3 manage.py migrate dcim 0049 --fake

This will reset the recorded migrations to a pre-2.3 state. You should see an output like this:

# python3 manage.py migrate circuits 0009 --fake
Operations to perform:
Target specific migration: 0009_unicode_literals, from circuits
Running migrations:
Rendering model states... DONE
Unapplying circuits.0010_circuit_status... FAKED
# python3 manage.py migrate dcim 0049 --fake
Operations to perform:
Target specific migration: 0049_rackreservation_change_user, from dcim
Running migrations:
Rendering model states... DONE
Unapplying dcim.0055_virtualchassis_ordering... FAKED
Unapplying dcim.0054_site_status_timezone_description... FAKED
Unapplying dcim.0053_platform_manufacturer... FAKED
Unapplying dcim.0052_virtual_chassis... FAKED
Unapplying dcim.0051_rackreservation_tenant... FAKED
Unapplying dcim.0050_interface_vlan_tagging... FAKED

Next, run "python3 manage.py showmigrations dcim". You should see that migrations 0050 through 0055 (inclusive) are no longer marked as applied:

# python3 manage.py showmigrations dcim

dcim
[X] 0001_initial
[X] 0002_auto_20160622_1821

...
[X] 0048_rack_serial
[X] 0049_rackreservation_change_user
[ ] 0050_interface_vlan_tagging
[ ] 0051_rackreservation_tenant
[ ] 0052_virtual_chassis
[ ] 0053_platform_manufacturer
[ ] 0054_site_status_timezone_description
[ ] 0055_virtualchassis_ordering

Finally, try running a normal migration with "python3 manage.py migrate". It should detect and apply the v2.3 migrations correctly.

# python3 manage.py migrate

Operations to perform:
Apply all migrations: admin, auth, circuits, contenttypes, dcim, extras, ipam, secrets, sessions, tenancy, users, virtualization

Running migrations:
Applying circuits.0010_circuit_status... OK
Applying dcim.0050_interface_vlan_tagging... OK
Applying dcim.0051_rackreservation_tenant... OK
Applying dcim.0052_virtual_chassis... OK
Applying dcim.0053_platform_manufacturer... OK
Applying dcim.0054_site_status_timezone_description... OK
Applying dcim.0055_virtualchassis_ordering... OK

Please let me know if that works.

Jeremy

To unsubscribe from this group and stop receiving emails from it, send an email to netbox-discuss+unsubscribe@googlegroups.com.
To post to this group, send email to netbox-discuss@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/netbox-discuss/9e634bb3-1f98-43a6-b92c-d34ba6669a47%40googlegroups.com.

Simen Linderud

unread,

Feb 27, 2018, 10:59:48 AM2/27/18

to NetBox

On my side this was the result.

Sorry if it seems like i am hijacking this post.

But i also tested the Beta version. So our issues should be quite similar.

python3 manage.py migrate

Operations to perform:

Apply all migrations: admin, auth, circuits, contenttypes, dcim, extras, ipam, secrets, sessions, tenancy, users, virtualization

Running migrations:

Applying circuits.0010_circuit_status...Traceback (most recent call last):

File "/usr/local/lib/python3.6/dist-packages/django/db/backends/utils.py", line 64, in execute

return self.cursor.execute(sql, params)

psycopg2.ProgrammingError: column "status" of relation "circuits_circuit" already exists

The above exception was the direct cause of the following exception:

Traceback (most recent call last):

File "manage.py", line 10, in <module>

execute_from_command_line(sys.argv)

File "/usr/local/lib/python3.6/dist-packages/django/core/management/__init__.py", line 364, in execute_from_command_line

utility.execute()

File "/usr/local/lib/python3.6/dist-packages/django/core/management/__init__.py", line 356, in execute

self.fetch_command(subcommand).run_from_argv(self.argv)

File "/usr/local/lib/python3.6/dist-packages/django/core/management/base.py", line 283, in run_from_argv

self.execute(*args, **cmd_options)

File "/usr/local/lib/python3.6/dist-packages/django/core/management/base.py", line 330, in execute

output = self.handle(*args, **options)

File "/usr/local/lib/python3.6/dist-packages/django/core/management/commands/migrate.py", line 204, in handle

fake_initial=fake_initial,

File "/usr/local/lib/python3.6/dist-packages/django/db/migrations/executor.py", line 115, in migrate

state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial)

File "/usr/local/lib/python3.6/dist-packages/django/db/migrations/executor.py", line 145, in _migrate_all_forwards

state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial)

File "/usr/local/lib/python3.6/dist-packages/django/db/migrations/executor.py", line 244, in apply_migration

state = migration.apply(state, schema_editor)

File "/usr/local/lib/python3.6/dist-packages/django/db/migrations/migration.py", line 129, in apply

operation.database_forwards(self.app_label, schema_editor, old_state, project_state)

File "/usr/local/lib/python3.6/dist-packages/django/db/migrations/operations/fields.py", line 88, in database_forwards

field,

File "/usr/local/lib/python3.6/dist-packages/django/db/backends/base/schema.py", line 429, in add_field

self.execute(sql, params)

File "/usr/local/lib/python3.6/dist-packages/django/db/backends/base/schema.py", line 120, in execute

cursor.execute(sql, params)

File "/usr/local/lib/python3.6/dist-packages/django/db/backends/utils.py", line 64, in execute

return self.cursor.execute(sql, params)

File "/usr/local/lib/python3.6/dist-packages/django/db/utils.py", line 94, in __exit__

six.reraise(dj_exc_type, dj_exc_value, traceback)

File "/usr/local/lib/python3.6/dist-packages/django/utils/six.py", line 685, in reraise

raise value.with_traceback(tb)

File "/usr/local/lib/python3.6/dist-packages/django/db/backends/utils.py", line 64, in execute

return self.cursor.execute(sql, params)

django.db.utils.ProgrammingError: column "status" of relation "circuits_circuit" already exists

f...@23media.de

unread,

Feb 27, 2018, 11:00:49 AM2/27/18

to NetBox

Thanks for the quick workaround everything till the migrate works as expected. But the migrate job didn't worked, here is the output:

Operations to perform:
  Apply all migrations: admin, auth, circuits, contenttypes, dcim, extras, ipam, secrets, sessions, tenancy, users, virtualization
Running migrations:

Applying circuits.0010_circuit_status...Traceback (most recent call last):

File "/usr/lib/python3.4/site-packages/django/db/backends/utils.py", line 64, in execute

    return self.cursor.execute(sql, params)
psycopg2.ProgrammingError: column "status" of relation "circuits_circuit" already exists


The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "manage.py", line 10, in <module>
    execute_from_command_line(sys.argv)

  File "/usr/lib/python3.4/site-packages/django/core/management/__init__.py", line 364, in execute_from_command_line
    utility.execute()
  File "/usr/lib/python3.4/site-packages/django/core/management/__init__.py", line 356, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/lib/python3.4/site-packages/django/core/management/base.py", line 283, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/usr/lib/python3.4/site-packages/django/core/management/base.py", line 330, in execute
    output = self.handle(*args, **options)
  File "/usr/lib/python3.4/site-packages/django/core/management/commands/migrate.py", line 204, in handle
    fake_initial=fake_initial,
  File "/usr/lib/python3.4/site-packages/django/db/migrations/executor.py", line 115, in migrate

state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial)

File "/usr/lib/python3.4/site-packages/django/db/migrations/executor.py", line 145, in _migrate_all_forwards

state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial)

  File "/usr/lib/python3.4/site-packages/django/db/migrations/executor.py", line 244, in apply_migration
    state = migration.apply(state, schema_editor)
  File "/usr/lib/python3.4/site-packages/django/db/migrations/migration.py", line 129, in apply
    operation.database_forwards(self.app_label, schema_editor, old_state, project_state)
  File "/usr/lib/python3.4/site-packages/django/db/migrations/operations/fields.py", line 88, in database_forwards
    field,
  File "/usr/lib/python3.4/site-packages/django/db/backends/base/schema.py", line 429, in add_field
    self.execute(sql, params)
  File "/usr/lib/python3.4/site-packages/django/db/backends/base/schema.py", line 120, in execute
    cursor.execute(sql, params)
  File "/usr/lib/python3.4/site-packages/django/db/backends/utils.py", line 64, in execute
    return self.cursor.execute(sql, params)
  File "/usr/lib/python3.4/site-packages/django/db/utils.py", line 94, in __exit__
    six.reraise(dj_exc_type, dj_exc_value, traceback)
  File "/usr/lib/python3.4/site-packages/django/utils/six.py", line 685, in reraise
    raise value.with_traceback(tb)
  File "/usr/lib/python3.4/site-packages/django/db/backends/utils.py", line 64, in execute

    return self.cursor.execute(sql, params)
django.db.utils.ProgrammingError: column "status" of relation "circuits_circuit" already exists

Showmigrations shows still 50-55 unmarked.

Jeremy Stretch

unread,

Feb 27, 2018, 11:08:39 AM2/27/18

to f...@23media.de, NetBox

Alright, so it looks like you both still have the applied migrations from the beta. Let's return to marking all migrations as applied:

python3 manage.py migrate --fake

Next, we're going to actually reverse the migrations to a pre-2.3 state. To do this, checkout the v2.3 beta branch (either beta1 or beta2, whichever you used), and revert the DCIM migrations back to 0049:

git checkout -b v2.3-beta2

python3 manage.py migrate dcim 0049

Then, switch back to the v2.3.0 release and try applying the migrations forward:

git checkout -b master
python3 manage.py migrate

Hopefully this will complete without error.

To unsubscribe from this group and stop receiving emails from it, send an email to netbox-discuss+unsubscribe@googlegroups.com.
To post to this group, send email to netbox-discuss@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/netbox-discuss/33d2838e-5709-427b-9fad-da3c154b0568%40googlegroups.com.

f...@23media.de

unread,

Feb 27, 2018, 1:13:35 PM2/27/18

to NetBox

Hi Jeremy,

the migrate --fake works. But got trouble with the further steps:

fatal: A branch named 'master' already exists.

if im using git checkout v2.3-beta2

and the migrate doesn't work, too.

Operations to perform:
  Target specific migration: 0049_rackreservation_change_user, from dcim
Running migrations:
  Rendering model states... DONE

  Unapplying dcim.0054_site_status_timezone_description... OK
  Unapplying dcim.0053_platform_manufacturer... OK
  Unapplying dcim.0052_virtual_chassis...Traceback (most recent call last):

  File "manage.py", line 10, in <module>
    execute_from_command_line(sys.argv)
  File "/usr/lib/python3.4/site-packages/django/core/management/__init__.py", line 364, in execute_from_command_line
    utility.execute()
  File "/usr/lib/python3.4/site-packages/django/core/management/__init__.py", line 356, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/lib/python3.4/site-packages/django/core/management/base.py", line 283, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/usr/lib/python3.4/site-packages/django/core/management/base.py", line 330, in execute
    output = self.handle(*args, **options)
  File "/usr/lib/python3.4/site-packages/django/core/management/commands/migrate.py", line 204, in handle
    fake_initial=fake_initial,

  File "/usr/lib/python3.4/site-packages/django/db/migrations/executor.py", line 119, in migrate
    state = self._migrate_all_backwards(plan, full_plan, fake=fake)
  File "/usr/lib/python3.4/site-packages/django/db/migrations/executor.py", line 194, in _migrate_all_backwards
    self.unapply_migration(states[migration], migration, fake=fake)
  File "/usr/lib/python3.4/site-packages/django/db/migrations/executor.py", line 264, in unapply_migration
    state = migration.unapply(state, schema_editor)
  File "/usr/lib/python3.4/site-packages/django/db/migrations/migration.py", line 178, in unapply
    operation.database_backwards(self.app_label, schema_editor, from_state, to_state)
  File "/usr/lib/python3.4/site-packages/django/db/migrations/operations/models.py", line 540, in database_backwards
    return self.database_forwards(app_label, schema_editor, from_state, to_state)
  File "/usr/lib/python3.4/site-packages/django/db/migrations/operations/models.py", line 536, in database_forwards
    getattr(new_model._meta, self.option_name, set()),
  File "/usr/lib/python3.4/site-packages/django/db/backends/base/schema.py", line 349, in alter_unique_together
    self._delete_composed_index(model, fields, {'unique': True}, self.sql_delete_unique)
  File "/usr/lib/python3.4/site-packages/django/db/backends/base/schema.py", line 378, in _delete_composed_index
    ", ".join(columns),
ValueError: Found wrong number (0) of constraints for dcim_device(virtual_chassis_id, vc_position)

Already think about to load a backup, exporting the CSVs and import them to a new system.

Message has been deleted

Simen Linderud

unread,

Feb 28, 2018, 4:36:11 AM2/28/18

to NetBox

This time i got a different result:



netbox$ python3 manage.py migrate

Traceback (most recent call last):
  File "manage.py", line 10, in <module>
    execute_from_command_line(sys.argv)


  File "/usr/local/lib/python3.6/dist-packages/django/core/management/__init__.py", line 364, in execute_from_command_line
    utility.execute()
  File "/usr/local/lib/python3.6/dist-packages/django/core/management/__init__.py", line 356, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/local/lib/python3.6/dist-packages/django/core/management/base.py", line 283, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/usr/local/lib/python3.6/dist-packages/django/core/management/base.py", line 330, in execute
    output = self.handle(*args, **options)
  File "/usr/local/lib/python3.6/dist-packages/django/core/management/commands/migrate.py", line 86, in handle
    executor.loader.check_consistent_history(connection)
  File "/usr/local/lib/python3.6/dist-packages/django/db/migrations/loader.py", line 298, in check_consistent_history
    connection.alias,
django.db.migrations.exceptions.InconsistentMigrationHistory: Migration dcim.0055_virtualchassis_ordering is applied before its dependency dcim.0054_site_status_timezone_description on database 'default'.

Simen Linderud

unread,

Feb 28, 2018, 8:44:46 AM2/28/18

to NetBox

Solved it by reverting whatever 0055 did and removing the migration as done.

I wouldn't recommend doing it this way... And for all i know something is still broke.