Page MenuHomePhabricator

cloudnet VLAN Netbox discrepancies
Closed, ResolvedPublic

Description

As a result of an audit (see parent task) I've noticed some discrepancies between the data in Netbox and that in PuppetDB for the cloudnet hosts. If running again the PuppetDB import script it would update the VLAN allocation for one interface per-host.

The affected hosts are:
cloudnet1003 cloudnet1004 cloudnet2002-dev cloudnet2004-dev

And the related interfaces (switch side) are;

asw2-b7-eqiad: updating vlans for interface xe-7/0/19
asw2-b4-eqiad: updating vlans for interface xe-4/0/46
asw-b5-codfw: updating vlans for interface ge-5/0/42
asw-b1-codfw: updating vlans for interface ge-1/0/27

If the changes are correct (i.e. PuppetDB is reporting correctly and Netbox is out of date), to fix the Netbox side is sufficient to run https://netbox.wikimedia.org/extras/scripts/interface_automation.ImportPuppetDB/ with the affected hosts as input:
cloudnet1003 cloudnet1004 cloudnet2002-dev cloudnet2004-dev
and then check with Homer that there are no pending changes on the switches.

Related Objects

StatusSubtypeAssignedTask
OpenNone
ResolvedVolans

Event Timeline

Volans claimed this task.

After verifying that the changes were all expected and the VLAN bits were actually an artifact of how Netbox represents the data compared to some default values that changed (null vs ""), I've run the script on the above hosts. Results are in https://netbox.wikimedia.org/extras/changelog/?request_id=4fae8a74-ecf1-42ee-bcb3-74c0eab224fd
Resolving.