Unable to assign BGP models to custom fields
NetBox version
4.0.9 with BGP plugin 0.13.2
Describe the bug
When creating a new custom field via the Netbox UI it's not possible to select any of the BGP models for assignment.
To Reproduce Steps to reproduce the behavior:
- Go to
/extras/custom-fields/add/on your Netbox install - Try selecting a BGP plugin model from the
Object typesdropdown - See that none of the BGP models can be selected
Expected behavior
I expect to be able to assign custom fields to some of the BGP models, mostly sessions where the custom fields are documented in the API.
Screenshots
n/a
Additional context
n/a
I'm not able to reproduce your issue, would you mind to share further information ?
I'm also not able to replicate this. I'm removing the label bug for now pending further information from @mraerino mraerino
ok, this does indeed not happen on a fresh install, only on our existing install that has existed for many netbox versions
i wonder if there is some dirty database state causing this. it's very strange.
I have this problem too but it is inconsistent as @mraerino mentions.
Netbox: 4.0.11 Netbox BGP: 0.13.3
My local fresh-ish instance running these versions (with prod database imported) I don't experience this at all. I can make custom fields on the BGP plugin without any problem. However in our production and test environments I experience this problem as described - the BGP plugin objects are not searchable. For a workaround I could create the custom field using API without any issue.
I've set this to pending close (as is the primary issue) as there's no easy way to replicate it - it would literally need a copy of databases to see why this occurs - its something database related.
hi @mraerino and @rvtipper - could you please provide the PLUGINS=[] line from your configuration please when this is occurring ? - this is not a netbox-bgp issue but we have a potential candidate but I'll need this information to ascertain if this mirrors the occurrence I'm aware of
@cruse1977 ah interesting, the order I give the plugins matters for me. I am also running with the netbox secrets plugin (2.0.3), if that config line reads PLUGINS = ["netbox_bgp", "netbox_secrets"] then I can select BGP objects ok for tags and custom fields, if netbox secrets is given first then I can't. In both instances I can select netbox secrets objects ok.
So the other case I'm aware of - also had netbox-secrets as the penultimate plugin prior to the one with model issues, swap secrets to the latter and its fine. Thats two cases and the other plugin wasn't BGP - thanks for coming back @rvtipper
Closing this issue out - its not an issue with BGP, more likely secrets.
Could be related to https://github.com/netbox-community/netbox/discussions/17836