Skip to content

Prepare v1.9.0 release - #570

Open
bb-Ricardo wants to merge 183 commits into
mainfrom
development
Open

bb-Ricardo wants to merge 183 commits into
mainfrom
development

Conversation

@bb-Ricardo

Copy link
Copy Markdown
Owner

Merges v1.9.0 Release

pto-centrica and others added 30 commits February 26, 2025 09:18
…t-site-issue

fix: only set the Cluster scope_type if the site_name is not None
fix: handle object and multi-object custom fields correctly
Sergey Sannikov and others added 29 commits September 10, 2026 03:39
vmware: add vm_status_on_create and vm_status_preserve
netbox: add orphaned_device_status and orphaned_vm_status
fix: scope a cluster with the site object so NetBox accepts it
…tive IP removal

Old TMOS builds (e.g. BIG-IP 11.5.0, 12.1.4.1) report VMware Tools as
running but never populate per-NIC guest.net data. That caused every
interface's NetBox IP assignment on those VMs to look "removed" on
each sync cycle and get deleted, even though the guest is up and the
IP is still live. Skip IP handling for a VM when guest.net comes back
completely empty while tools report running; a real per-NIC removal
still reports the NIC (just without an IP), so that case is unaffected.

(cherry picked from commit 261e338)
vmware: keep IPs when guest tools report no interface at all
check_redfish: stop syncing the live fan reading
Signed-off-by: Ricardo Bartels <ricardo.bartels@telekom.de>
Signed-off-by: Ricardo Bartels <ricardo.bartels@telekom.de>
Modules were only added to dependent_netbox_objects when
model_components_as_modules was on. On a run with the option off, interfaces
and power ports created by an earlier modules-on run still reference a module,
and NetBox reports that relation as an object the run never loaded, so every
such object logged 'Problems resolving relation module'. Reproduced on a live
NetBox 4.4.5: turning the option off logged the error for every interface and
power port of a host previously synced with modules.

Read the module objects back on every run instead; the option keeps gating
whether components are *created* as modules, not whether existing ones can be
resolved. A second modules-on run stays a no-op and the option-off run resolves
cleanly (it then models the components as inventory items and orphans the old
modules, as before).
fix: assign addresses with a non-unique role to every interface
check_redfish: model components as NetBox modules
vmware: create cables from ESXi CDP/LLDP neighbours, behind sync_host_cables
Signed-off-by: Ricardo Bartels <ricardo.bartels@telekom.de>
Signed-off-by: Ricardo Bartels <ricardo.bartels@telekom.de>
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

Successfully merging this pull request may close these issues.