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

Cannot assign contact to prefix in 3.7 #14891

Closed
konsta21 opened this issue Jan 22, 2024 · 1 comment
Closed

Cannot assign contact to prefix in 3.7 #14891

konsta21 opened this issue Jan 22, 2024 · 1 comment

Comments

@konsta21
Copy link

Deployment Type

Self-hosted

NetBox Version

v3.7.1

Python Version

3.10

Steps to Reproduce

  1. Create sample prefix. In my case the sample prefix ID is "645"
  2. Create sample contact named "Sample Contact". In my case the sample contact ID is "25"
  3. Create sample contact role named "Sample Contact Role"
  4. Click on "Contact Assignment" option:
    image
  5. Then add the following text with the "Import" button:
    content_type,object_id,contact.id,role
    'ipam.prefix',645,25,'Sample Contact Role'

Expected Behavior

The operation should be successful and prefix object should receive a contact assigned to it. Although contact is not visible from the prefix side:
image

It can be seen as existing from the "Contact Assignment" tab:
image

Observed Behavior

In previous version (e.g. 3.6.6) this worked fine. However, with the new 3.7 and 3.7.1 it errors with:
Annotation 2024-01-22 175452

Interestingly, this process works fine when trying the same approach to import a contact to a device, as seen here:
image

@konsta21 konsta21 added the type: bug A confirmed report of unexpected behavior in the application label Jan 22, 2024
@jeremystretch
Copy link
Member

Assigning a contact to a prefix is not currently supported. There is a feature request open to implement this; please see #13764.

@jeremystretch jeremystretch closed this as not planned Won't fix, can't repro, duplicate, stale Jan 22, 2024
@jeremystretch jeremystretch removed the type: bug A confirmed report of unexpected behavior in the application label Jan 22, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 22, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants