Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to assign BGP models to custom fields #212

Open
mraerino opened this issue Sep 29, 2024 · 3 comments
Open

Unable to assign BGP models to custom fields #212

mraerino opened this issue Sep 29, 2024 · 3 comments
Assignees
Labels
revisions-needed Revisions are need to ascertain the issue

Comments

@mraerino
Copy link

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:

  1. Go to /extras/custom-fields/add/ on your Netbox install
  2. Try selecting a BGP plugin model from the Object types dropdown
  3. 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

@mraerino mraerino added the bug Something isn't working label Sep 29, 2024
@pl0xym0r
Copy link
Contributor

I'm not able to reproduce your issue, would you mind to share further information ?
image
image

@cruse1977
Copy link
Member

cruse1977 commented Oct 7, 2024

I'm also not able to replicate this. I'm removing the label bug for now pending further information from @mraerino mraerino

@cruse1977 cruse1977 removed the bug Something isn't working label Oct 7, 2024
@cruse1977 cruse1977 self-assigned this Oct 7, 2024
@cruse1977 cruse1977 added the revisions-needed Revisions are need to ascertain the issue label Oct 7, 2024
@mraerino
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
revisions-needed Revisions are need to ascertain the issue
Projects
None yet
Development

No branches or pull requests

3 participants