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

Handle inherited associations same as direct #2202

Closed
alesz opened this issue Jun 27, 2018 · 1 comment
Closed

Handle inherited associations same as direct #2202

alesz opened this issue Jun 27, 2018 · 1 comment
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@alesz
Copy link

alesz commented Jun 27, 2018

Issue type

[ ] Feature request
[x] Bug report
[ ] Documentation

Environment

  • Python version: 3.6
  • NetBox version: 2.3.4

Description

Steps to reproduce:

  1. Add tenant A
  2. Add vrf B and associate it with tenant A
  3. Add prefix C and associate it with vrf B. Don't associate with tenant A.

Observed:

Displaying prefix C shows Tenant A with Inherited tag. Displaying tenant A counts prefix C in stats. Prefix is associated with tenant via vrf object (inherited tag) if tenant field is not set.
Clicking on prefixes in tenant A stats opens /ipam/prefixes/?tenant=A.

Error:

List of prefixes is empty, tenant search filter shows A(0). Setting tenant to -- None -- displays prefix correctly.

Expected:

prefix behaves in same way with inherited tenant as with associated one.

@jeremystretch jeremystretch added type: bug A confirmed report of unexpected behavior in the application status: accepted This issue has been accepted for implementation labels Jun 29, 2018
@jeremystretch
Copy link
Member

I think this highlights how fragile the concept of inherited tenancy is, not to mention that it's completely absent in the REST API. I think we're better off just ditching it.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

2 participants