Device Management IPv4 Address shows erroneous text "(NAT:)" when IP has no NAT associations #6829

Closed
opened 2025-12-29 19:45:51 +01:00 by adam · 1 comment
Owner

Originally created by @ZPrimed on GitHub (Aug 18, 2022).

Originally assigned to: @atownson on GitHub.

NetBox version

v3.3.0

Python version

3.8

Steps to Reproduce

This is a minor / Display Bug

I am seeing this on all Device instances in my installation (which was upgraded from 3.2.8 to 3.3.0).
It is also reproducible on a newly-created Device / Interface / IP combo.

  1. Create a Device with at least one Interface
  2. Set (or create) an IP Address on that Interface, and check the box to make it the "Primary IP for this device" (i.e. management address)
  3. View the Device's overview page, note that in the "Management" box there is the text "(NAT:)" after the IP address

Screenshot from my own installation with a pre-existing device:
image

Expected Behavior

Would not expect to see any information about NAT when the IP address has no NAT relationships defined. (Suspect this is related to the change in the nat_outside relation to return zero or more IPs instead of the past "None or one"?)

Observed Behavior

UI displays spurious "(NAT:)" text when it shouldn't

Originally created by @ZPrimed on GitHub (Aug 18, 2022). Originally assigned to: @atownson on GitHub. ### NetBox version v3.3.0 ### Python version 3.8 ### Steps to Reproduce This is a **minor** / Display Bug I am seeing this on *all* Device instances in my installation (which was upgraded from 3.2.8 to 3.3.0). It is also reproducible on a newly-created Device / Interface / IP combo. 1. Create a Device with at least one Interface 2. Set (or create) an IP Address on that Interface, and check the box to make it the "Primary IP for this device" (i.e. management address) 3. View the Device's overview page, note that in the "Management" box there is the text "(NAT:)" after the IP address Screenshot from my own installation with a pre-existing device: ![image](https://user-images.githubusercontent.com/4011850/185256582-5d75ec97-d5d4-4820-846e-046bb0a9cfaa.png) ### Expected Behavior Would not expect to see any information about NAT when the IP address has no NAT relationships defined. (Suspect this is related to the change in the `nat_outside` relation to return zero or more IPs instead of the past "None or one"?) ### Observed Behavior UI displays spurious "(NAT:)" text when it shouldn't
adam added the type: bugstatus: accepted labels 2025-12-29 19:45:51 +01:00
adam closed this issue 2025-12-29 19:45:51 +01:00
Author
Owner

@atownson commented on GitHub (Aug 18, 2022):

I can work on this.

@atownson commented on GitHub (Aug 18, 2022): I can work on this.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#6829