How could to add a devices bay to parent devices

[ngocnd1]

Hi anyone,
I got an error "This type of devices is not support devices bay" event i already config server type as parent and children
Example: Server 1: parent and 6U
Server 2: children and 0U(it's must be 0U if we want to mark role as children)
Anyone can help?

[candlerb]

You have to create device bays in the parent device type.

You may also need to create device bays in the device itself - if you've already created the device, but the device type didn't have device bays at the time you created it. That's because components are only copied from device type to device at the time the device is created.

[ngocnd1]

Thanks @candlerb I already created devices bay successfully

[candlerb]

It Works For Me™, so please specify what Netbox version you're using, and if you can replicate it in demo.netbox.dev, give the exact sequence of steps you are following.

Check that Server 1's device type is marked "parent", that the actual device Server 1 has device bays present (not just in the device type that server 1 was built from)

Check that Server 2's device type is marked "child".

Also, can you explain the relationship between "Server 1" and "Server 2"? If Server 1 is a blade chassis, and Server 2 is a server blade, then parent/child relationship is the right one to use. But then you wouldn't normally call the chassis "Server 1".

[ngocnd1]

@candlerb
Hi, another question
I got an error when i upgrade to verson 3.5.3

[root@osteam-netbox-03 netbox]# python3.9 manage.py migrate
Operations to perform:
Apply all migrations: admin, auth, circuits, contenttypes, core, dcim, django_rq, extras, ipam, sessions, social_django, taggit, tenancy, users, virtualization, wireless
Running migrations:
Applying circuits.0042_provideraccount...Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/django/db/backends/utils.py", line 89, in _execute
return self.cursor.execute(sql, params)
psycopg2.errors.InsufficientPrivilege: must be owner of table circuits_provider

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

Traceback (most recent call last):
File "/opt/netbox/netbox/manage.py", line 10, in
execute_from_command_line(sys.argv)
File "/usr/local/lib/python3.9/site-packages/django/core/management/init.py", line 446, in execute_from_command_line
utility.execute()
File "/usr/local/lib/python3.9/site-packages/django/core/management/init.py", line 440, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/usr/local/lib/python3.9/site-packages/django/core/management/base.py", line 402, in run_from_argv
self.execute(*args, **cmd_options)
File "/usr/local/lib/python3.9/site-packages/django/core/management/base.py", line 448, in execute
output = self.handle(*args, **options)
File "/usr/local/lib/python3.9/site-packages/django/core/management/base.py", line 96, in wrapped
res = handle_func(*args, **kwargs)
File "/usr/local/lib/python3.9/site-packages/django/core/management/commands/migrate.py", line 349, in handle
post_migrate_state = executor.migrate(
File "/usr/local/lib/python3.9/site-packages/django/db/migrations/executor.py", line 135, in migrate
state = self._migrate_all_forwards(
File "/usr/local/lib/python3.9/site-packages/django/db/migrations/executor.py", line 167, in _migrate_all_forwards
state = self.apply_migration(
File "/usr/local/lib/python3.9/site-packages/django/db/migrations/executor.py", line 252, in apply_migration
state = migration.apply(state, schema_editor)
File "/usr/local/lib/python3.9/site-packages/django/db/migrations/migration.py", line 130, in apply
operation.database_forwards(
File "/usr/local/lib/python3.9/site-packages/django/db/migrations/operations/fields.py", line 170, in database_forwards
schema_editor.remove_field(
File "/usr/local/lib/python3.9/site-packages/django/db/backends/base/schema.py", line 724, in remove_field
self.execute(sql)
File "/usr/local/lib/python3.9/site-packages/django/db/backends/base/schema.py", line 199, in execute
cursor.execute(sql, params)
File "/usr/local/lib/python3.9/site-packages/django/db/backends/utils.py", line 67, in execute
return self._execute_with_wrappers(
File "/usr/local/lib/python3.9/site-packages/django/db/backends/utils.py", line 80, in _execute_with_wrappers
return executor(sql, params, many, context)
File "/usr/local/lib/python3.9/site-packages/django/db/backends/utils.py", line 89, in _execute
return self.cursor.execute(sql, params)
File "/usr/local/lib/python3.9/site-packages/django/db/utils.py", line 91, in exit
raise dj_exc_value.with_traceback(traceback) from exc_value
File "/usr/local/lib/python3.9/site-packages/django/db/backends/utils.py", line 89, in _execute
return self.cursor.execute(sql, params)
django.db.utils.ProgrammingError: must be owner of table circuits_provider

As my understanding it is new feature "provider account"
How do i migrate db in right ways, because i still have a lot of data in DB then i dont want to drop it.
Thanks

[candlerb]

django.db.utils.ProgrammingError: must be owner of table circuits_provider

Postgres permissions problem: #11314 (comment), #11811 (reply in thread)

[ngocnd1]

@candlerb i knew that solution because already update new version 1 month ago
I already did it before but isn't work, currently i using version 3.4.6 and i saw that version 3.5.3 has new feature provider account and it need to create an table for it and made that error.

[candlerb]

The same upgrade worked for me, hence tou have some other permissions problem on your system.

I have in the past seen users who have somehow created all their tables owned by "postgres" instead of "netbox", which can be fixed by changing the owner of the table.

See:
#6233 (comment)
#6233 (reply in thread)
#6233 (reply in thread)
#6233 (reply in thread)

Also:
#6231
#8396