Open wuetz opened 7 months ago
I can confirm that I'm seeing the same thing with a new install with Netbox 3.7.3.
I have forked, updated for 3.7 and re-published the plugin as netbox-topology-plugin.
I have not made an effort to import in any existing plugin settings though, however if you want you could simply dump the old table and import it into the new table.
I am not able to clone the repo: remote: Repository not found. fatal: repository 'https://github.com/DanSheps/netbox-topology-plugin-plugin/' not found
I managed to install the forked repo from @DanSheps using netbox-topology-plugin
instead of netbox-topology-plugin-plugin
thanks Bogdan, that was actually the issue - didn't validate it, just copy/paste
Thanks everyone for you patience. I've just released a compatibility fix for NetBox 3.6, 3.7, and newly released 4.0.
As the title states out, we upgraded Netbox from 3.3.1 to 3.7.2. In 3.3.1 no issues were recognized. During the upgrade process of netbox ( at the step where upgrade.sh is triggered see: https://docs.netbox.dev/en/stable/installation/upgrading/ ) we received the first errors:
I was able to successfully do the netbox upgarde by disabling the plugin in the
configuration.py
. Then I re-enabled the plugin. But as soon asnetbox-rq
is getting started started the very same errors appear in the logs:The netbox-rq service is diing periodically.
Any remarks on this?