Skip to content

overwrite_vm_tenant option #454

Open

Description

@mertoktem29

We have different tenants on different vcenter. I am changing vm tenant on netbox but when start netbox-sync ,vm tenant names are reverting to their old state. Is there any option the close overwrite_vm_tenant ?

Activity

  1. bb-Ricardo commented on Apr 10, 2025

    @bb-Ricardo
    Owner

    Hi @mertoktem29,

    have you defined the vm_tenant_relation setting?

  2. mertoktem29 commented on Apr 10, 2025

    @mertoktem29
    Author

    hello @bb-Ricardo , Can I close the overwrite here? As I understand i have to add vm one by one or i have to determine a pattern for vms right? I have too many vms with different name which i cant determine to pattern.

  3. bb-Ricardo commented on Apr 10, 2025

    @bb-Ricardo
    Owner

    Or just disable the option and then no tenants are assigned.

  4. bb-Ricardo commented on Jun 17, 2025

    @bb-Ricardo
    Owner

    were you able to solve this issue?

  5. marvinwankersteen commented on Jun 23, 2025

    @marvinwankersteen

    This may not fit in here, but is there a way to use the folder name in which the VM is located in VMware as the tenant?

  6. bb-Ricardo commented on Jun 23, 2025

    @bb-Ricardo
    Owner

    This may not fit in here, but is there a way to use the folder name in which the VM is located in VMware as the tenant?

    Hi, it is currently not possible to source the tenant name from the VMware folder.

  7. semx commented on Oct 10, 2026

    @semx
    Collaborator

    Implemented in development (#589), in the image ghcr.io/bb-ricardo/netbox-sync:development. The option is called overwrite_vm_tenant and defaults to True, so nothing changes for existing setups. With overwrite_vm_tenant = False a tenant already set on a NetBox VM is kept whatever the relations resolve; a VM without a tenant still gets the resolved one. It sits next to overwrite_vm_platform and works the same way.

    Could you try it against your vCenter? Run with -n first, then a real run and a second one (the second should change nothing in NetBox), and say what came out, here or in the call for testing: #592. Nothing changes unless the option is set, so pulling the image is safe. It goes into 1.10.0, the next feature release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    awaiting replyAwaiting reply from issue owner

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions