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.

Sign up for GitHub

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

Jump to bottom

bug: de-allocted resources are not properly removed from a CoreNumberPool #4617

Open
wvandeun opened this issue Oct 11, 2024 · 1 comment
Open

bug: de-allocted resources are not properly removed from a CoreNumberPool #4617

wvandeun opened this issue Oct 11, 2024 · 1 comment
Labels
priority/2 This issue stalls work on the project or its dependents, it's a blocker for a release type/bug Something isn't working as expected
Milestone
Infrahub - 1.0

Comments

@wvandeun
Copy link
Contributor

Component

API Server / GraphQL

Infrahub version

0.16.3

Current Behavior

When you allocate a number from a number pool, to an attribute of a node and then remove the node, then the number stays allocated within the resource pool.

Expected Behavior

The number should be returned back to the pool as an available resource.

Steps to Reproduce

  • load infrahub with demo data and schema
  • create a number pool, node type InfraInterfaceL2, attribute speed
  • create a new L2 Interface, for the speed attribute use the number pool
  • delete the L2 interface
  • open the number resource pool detail page and click on the view button
  • the allocated number will show up twice in the list, referencing the id of the node that we deleted
    image

Additional Information

No response
@wvandeun wvandeun added type/bug Something isn't working as expected group/backend Issue related to the backend (API Server, Git Agent) labels Oct 11, 2024
@exalate-issue-sync exalate-issue-sync bot added priority/2 This issue stalls work on the project or its dependents, it's a blocker for a release and removed group/backend Issue related to the backend (API Server, Git Agent) labels Oct 11, 2024
@exalate-issue-sync exalate-issue-sync bot added this to the Infrahub - 1.0 milestone Oct 18, 2024
@exalate-issue-sync Exalate Issue Sync
Copy link

[From petercrocker]

Tagged for 1.0.0 if possible, this is affecting a customer who has to work around this now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority/2 This issue stalls work on the project or its dependents, it's a blocker for a release type/bug Something isn't working as expected
Projects
None yet
Milestone
Infrahub - 1.0
Development

No branches or pull requests
1 participant
@wvandeun