starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Attempting to create the next available prefix within a parent assigned to a VRF raises an AssertionError #1923

New Issue
Closed
opened 2025-12-29 17:20:36 +01:00 by adam · 0 comments
adam commented 2025-12-29 17:20:36 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Aug 8, 2018).

Environment

  • Python version: 3.5.6
  • NetBox version: 2.4.2

Steps to Reproduce

  1. Create a prefix assigned to a VRF.
  2. Make an API request to create the "next available" prefix within this prefix. For example:
curl -X POST \
-H "Authorization: Token <token>" \
-H "Content-Type: application/json" \
-H "Accept: application/json; indent=4" \
http://localhost:8000/api/ipam/prefixes/<pk>/available-prefixes/ \
--data '{"prefix_length": 26}'

Expected Behavior

A new child prefix should be created.

Observed Behavior

An exception is raised:

AssertionError: `HyperlinkedIdentityField` requires the request in the serializer context. Add `context={'request': request}` when instantiating the serializer.
Originally created by @jeremystretch on GitHub (Aug 8, 2018). ### Environment * Python version: 3.5.6 * NetBox version: 2.4.2 ### Steps to Reproduce 1. Create a prefix assigned to a VRF. 2. Make an API request to create the "next available" prefix within this prefix. For example: ``` curl -X POST \ -H "Authorization: Token <token>" \ -H "Content-Type: application/json" \ -H "Accept: application/json; indent=4" \ http://localhost:8000/api/ipam/prefixes/<pk>/available-prefixes/ \ --data '{"prefix_length": 26}' ``` ### Expected Behavior A new child prefix should be created. ### Observed Behavior An exception is raised: ``` AssertionError: `HyperlinkedIdentityField` requires the request in the serializer context. Add `context={'request': request}` when instantiating the serializer. ```
adam added the type: bugstatus: accepted labels 2025-12-29 17:20:36 +01:00
adam closed this issue 2025-12-29 17:20:36 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: accepted type: bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#1923
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?