[BUG]misleading error in whereabouts IPAM type

[rrajendran17]

Describe the bug
The following error is seen in whereabouts controller but the IPAM type is whereabouts and pods are allocated with correct ippool range.

E0331 22:21:08.718815 1 controller.go:290] "Unhandled Error" err="error syncing 'harvester-system/storagenetwork-gwxr6': only interested in networks whose IPAM type is 'whereabouts'. This one was: , requeuing" logger="UnhandledError"

The above error repeats periodically though the functionality is working fine.

Expected behavior
No error messages in whereabouts controller when functionality is working fine.Above errors are misleading for the user.

To Reproduce
Steps to reproduce the behavior:

1. Create a storage network for harvester which uses network attachment definition with ipam type whereabouts and specifying the ipool range

hp-65:~ # kubectl get settings storage-network -o yaml
apiVersion: harvesterhci.io/v1beta1
kind: Setting
metadata:
  annotations:
    storage-network.settings.harvesterhci.io/hash: c7b9e13c40a5be843d123424467c8f8563626120
    storage-network.settings.harvesterhci.io/net-attach-def: harvester-system/storagenetwork-rvnc5
    storage-network.settings.harvesterhci.io/old-net-attach-def: ""
  creationTimestamp: "2026-02-23T20:03:05Z"
  generation: 15
  name: storage-network
  resourceVersion: "39883826"
  uid: 95d905af-e33a-4694-b692-bebafa66bf7c
status:
  conditions:
  - lastUpdateTime: "2026-04-02T03:01:27Z"
    reason: Completed
    status: "True"
    type: configured
value: '{"vlan":15,"clusterNetwork":"mgmt","range":"15.0.0.0/24"}'

2.Network attachment definition is created by harvester when configuring the above storage network

kubectl get net-attach-def storagenetwork-rvnc5 -n harvester-system -o yaml
apiVersion: k8s.cni.cncf.io/v1
kind: NetworkAttachmentDefinition
metadata:
  annotations:
    storage-network.settings.harvesterhci.io: "true"
  creationTimestamp: "2026-04-02T03:01:25Z"
  finalizers:
  - wrangler.cattle.io/harvester-network-manager-nad-controller
  generateName: storagenetwork-
  generation: 1
  labels:
    network.harvesterhci.io/clusternetwork: mgmt
    network.harvesterhci.io/ready: "true"
    network.harvesterhci.io/type: L2VlanNetwork
    network.harvesterhci.io/vlan-id: "15"
    storage-network.settings.harvesterhci.io/hash: c7b9e13c40a5be843d123424467c8f8563626120
  name: storagenetwork-rvnc5
  namespace: harvester-system
  resourceVersion: "39883709"
  uid: 3768848e-61d0-4753-aa5b-25355062852c
spec:
  config: '{"cniVersion":"0.3.1","type":"bridge","bridge":"mgmt-br","promiscMode":true,"vlan":15,"ipam":{"type":"whereabouts","range":"15.0.0.0/24"}}'

3.secondary interface is created in instance manager pods and its allocated with ip address from the ippool range as expected

kubectl describe pod instance-manager-1abda1291959723fba381f2c5892240b -n longhorn-system
Name:                 instance-manager-1abda1291959723fba381f2c5892240b
Namespace:            longhorn-system
Priority:             2000000000
Priority Class Name:  system-cluster-critical
Service Account:      longhorn-service-account
Node:                 hp-65/10.115.13.220
Start Time:           Thu, 02 Apr 2026 03:01:28 +0000
Labels:               longhorn.io/component=instance-manager
                      longhorn.io/data-engine=v1
                      longhorn.io/instance-manager-image=imi-304e5903
                      longhorn.io/instance-manager-type=aio
                      longhorn.io/managed-by=longhorn-manager
                      longhorn.io/node=hp-65
Annotations:          cni.projectcalico.org/containerID: a1afd0aafe83d33d8f82af5299602212e625b5a10e43843f60093e3de49e6fed
                      cni.projectcalico.org/podIP: 10.52.0.66/32
                      cni.projectcalico.org/podIPs: 10.52.0.66/32
                      k8s.v1.cni.cncf.io/network-status:
                        [{
                            "name": "k8s-pod-network",
                            "interface": "eth0",
                            "ips": [
                                "10.52.0.66"
                            ],
                            "mac": "d6:75:fe:b0:66:c4",
                            "default": true,
                            "dns": {}
                        },{
                            "name": "harvester-system/storagenetwork-rvnc5",
                            "interface": "lhnet1",
                            "ips": [
                                "15.0.0.3"
                            ],
                            "mac": "96:99:d3:eb:ae:f3",
                            "dns": {}
                        }]
                      k8s.v1.cni.cncf.io/networks: [{"namespace": "harvester-system", "name": "storagenetwork-rvnc5", "interface": "lhnet1"}]
                      longhorn.io/last-applied-tolerations: [{"key":"kubevirt.io/drain","operator":"Exists","effect":"NoSchedule"}]
Status:               Running

4.The whereabouts controller logs shows below message periodically though the harvester-system/storagenetwork-rvnc5 network attachement defintion has correct IPAM type "whereabouts"

2026-04-06T05:09:56Z [debug] Used defaults from parsed flat file config @ /host/etc/cni/net.d/whereabouts.d/whereabouts.conf
E0406 05:09:56.315847       1 controller.go:290] "Unhandled Error" err="error syncing 'harvester-system/storagenetwork-rvnc5': only interested in networks whose IPAM type is 'whereabouts'. This one was: , requeuing" logger="UnhandledError"

Environment:

• Whereabouts version : 0.9.2
• Kubernetes version (use kubectl version): N/A
• Network-attachment-definition: N/A
• Whereabouts configuration (on the host): N/A
• OS (e.g. from /etc/os-release): N/A
• Kernel (e.g. uname -a): N/A
• Others: N/A

Additional info / context
Add any other information / context about the problem here.