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

Device bays and module bays aren’t properly propagated up to the parent object #158

Open
NEO-AMiGA opened this issue Nov 6, 2024 · 0 comments

Comments

@NEO-AMiGA
Copy link

'Controller A' and 'Controller B' was copied to the object with the ‘Add Device Type Components’ script. Controller A and B are not visible until I manually add another one on the object. And as seen on the tab, it only counts one. I guess/assume that this ‘Add Device Type Components’ doesn’t properly increase some counter on the parent? Is there a workaround or fix for this? I have seen it multiple times on modules and device bays and this in NetBox Community v4.1.2.

Screenshot 2024-11-06 at 08 31 56

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant