Unable to tag vlan for virtual machine in a cluster with no site

[nomad-cyanide]

I have just upgraded to 3.1.9 and is facing the issue of being unable to tag a vlan on a VM.

I have a virtual cluster X with no site, because it consist of 4 machines on site1 and 4 machines on site2, connected with layer2. The hosts have their site to match the site they are physically on, but the cluster is set to "none", because it cant have different site than its hosts.
Now on a VM on that cluster X, I am unable to tag a vlan in any vlan-group, even though I can select which vlan-group I want to tag from.
Am I missing something, or have I actually come across an error?

[mtinberg]

Would making a Site Group and associating the two Sites with it, then associating the VLAN Groups or VLANs with the Site Group instead of a Site help fix this? — Mark Tinberg ***@***.***> Division of Information Technology-Network Services University of Wisconsin-Madison Message ID: ***@***.***>

[nomad-cyanide]

Hi
We already have a site-group containing all the relevant sites and defined the vlan-groups as scope site-group pointing to the site-group mentioned first.
The odd thing is I can specify the vlan-group, but no vlans show up.

That VLAN-group contains 1400+ vlans.

[nomad-cyanide]

Did a little more testing.
It seems I can do the vlan-tagging via API (using my regular old scripts), but I cannot do it via the GUI, so it looks like a GUI interface-issue.

[cstueckrath]

we have the same problem with "un-sited" clusters

[nomad-cyanide]

There has been a new development in this.
It turns out that we can do the tagging in the test-instance, we have of netbox. The test-instance is basically a copy of prod, yet it is on the prod-instance we cannot tag vlans, where we can on the test-instance.
Could there be some permission issue or a database-issue? I find it unlikely, that it is a database issue, as the prod database has been replicated to test and it works in test.
edit This was a wrong statement. Read further below for clarification

[candlerb]

@nomad-cyanide @cstueckrath: if you can create a clear series of steps to reproduce the issue with a fresh Netbox 3.2 install, then it can be raised as a ticket.

For me: setting a virtual interface on a VM to mode "Access" and then selecting an untagged VLAN works fine; also setting the mode to "Tagged" and selecting a set of tagged VLANs works fine.

However there are lots of variables. In my case, the VLANs assigned to a particular site, and the VM cluster is assigned to the same site, and I'm not using VLAN groups. So you'll need to be specific around the circumstances required to reproduce this.

[cstueckrath]

• Cluster siteless
• any regional scoped VLAN Group (DCIM > location, region, site, site group)
• VLANs in that group

As it is not possible to assign a cluster to a Region or a Site group without assigning it to a site, the VLANs will not be available.
If the VLAN group is not scoped, VLANs are available for siteless clusters

Expected behaviour: Cluster Region and Site group are actually used and saved, even when no Site will be selected

[cstueckrath]

or make it possible for clusters to have multiple sites.

[nomad-cyanide]

Exactly.

[nomad-cyanide]

@nomad-cyanide @cstueckrath: if you can create a clear series of steps to reproduce the issue with a fresh Netbox 3.2 install, then it can be raised as a ticket.

I will, whenever I have the time to look at 3.2. Currently it doesn't look good. :(

For me: setting a virtual interface on a VM to mode "Access" and then selecting an untagged VLAN works fine; also setting the mode to "Tagged" and selecting a set of tagged VLANs works fine.

However there are lots of variables. In my case, the VLANs assigned to a particular site, and the VM cluster is assigned to the same site, and I'm not using VLAN groups. So you'll need to be specific around the circumstances required to reproduce this.

No, not a lot of variables.

• A Cluster X with no site assigned and a vm attached to that cluster
• All vlan-groups are either site or site-scopes. No vlan-groups are without site and have vlans defined
• Tagging a vm's in (cluster X) interface with a vlan is not possible in GUI. As it is possible using the API, I believe it is an error in the GUI, at least in version 3.1.9.