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

Can't use LAG as Parent to Virtual Interface #4436

Closed
mngan opened this issue Sep 12, 2023 · 2 comments · Fixed by #4583
Closed

Can't use LAG as Parent to Virtual Interface #4436

mngan opened this issue Sep 12, 2023 · 2 comments · Fixed by #4583
Assignees
Labels
emergent Unplanned work that is brought into a sprint after it's started. type: bug Something isn't working as expected

Comments

@mngan
Copy link

mngan commented Sep 12, 2023

Environment

  • Nautobot version (Docker tag too if applicable): 1.6.0
  • Python version: 3.9
  • Database platform, version: Postgres 14
  • Middleware(s):

Steps to Reproduce

  1. Create LAG interface ae0
  2. Create Virtual Interface ae0.0
  3. While creating Virtual interface, try to select LAG Interface as Parent

Expected Behavior

I was hoping that the LAG interface would be in the list of valid parents, but that does not seem to be the case.

Observed Behavior

It appears that only physical interfaces can be selected as parents. Is this expected? Or am I modeling the the subinterface of a LAG incorrectly? In this case, the sub interface is an IP interface not a switched interface. So using the Bridge model doesn't seem appropriate.

@mngan mngan added triage This issue is new and has not been reviewed. type: bug Something isn't working as expected labels Sep 12, 2023
@glennmatthews
Copy link
Contributor

Looks like the same issue as netbox-community/netbox#6106, which should be a very simple fix a la netbox-community/netbox@81193eb.

@glennmatthews glennmatthews removed the triage This issue is new and has not been reviewed. label Sep 13, 2023
@mngan
Copy link
Author

mngan commented Sep 13, 2023

This would work. I guess this will also fix the case of lo.0 and lo where both of these are virtual. I was going to work around this by making lo's interface type to other.

@bryanculver bryanculver added the emergent Unplanned work that is brought into a sprint after it's started. label Oct 2, 2023
@glennmatthews glennmatthews self-assigned this Oct 2, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
emergent Unplanned work that is brought into a sprint after it's started. type: bug Something isn't working as expected
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants