Logging shows timeout when deleting Apps

[cunningr]

Description

When we delete a pod and the driver tries to clean up, it can take some time to stop and deactivate the App on the device. We monitor this in a polling loop but it seems we may not wait long enough as we consistently see a timeout:

INFO[2026-02-03T09:53:20Z]restconf_client.go:126 Checking response ...
WARN[2026-02-03T09:53:22Z]app_hosting.go:159 App cvk0000_1e08ab44a5694f3c83a287a945ccabed did not reach ACTIVATED status after stop: timeout waiting for app cvk0000_1e08ab44a5694f3c83a287a945ccabed to reach status ACTIVATED after 30s
INFO[2026-02-03T09:53:22Z]app_hosting.go:162 Deactivating app cvk0000_1e08ab44a5694f3c83a287a945ccabed
INFO[2026-02-03T09:53:22Z]app_hosting.go:128 Deactivating app cvk0000_1e08ab44a5694f3c83a287a945ccabed
INFO[2026-02-03T09:53:23Z]app_hosting.go:135 Successfully deactivated app cvk0000_1e08ab44a5694f3c83a287a945ccabed
INFO[2026-02-03T09:53:23Z]app_hosting.go:190 Waiting for app cvk0000_1e08ab44a5694f3c83a287a945ccabed to reach status: DEPLOYED
INFO[2026-02-03T09:53:23Z]restconf_client.go:126 Checking response ...
INFO[2026-02-03T09:53:25Z]restconf_client.go:126 Checking response ...
INFO[2026-02-03T09:53:25Z]pod_lifecycle.go:130 Found container test-app -> app cvk0000_1e08ab44a5694f3c83a287a945ccabed
INFO[2026-02-03T09:53:25Z]pod_lifecycle.go:156 Found all 1 expected containers for pod default/dhcp-test-pod
INFO[2026-02-03T09:53:25Z]restconf_client.go:126 Checking response ...
INFO[2026-02-03T09:53:25Z]transformers.go:498 Container test-app (app: cvk0000_1e08ab44a5694f3c83a287a945ccabed) state: DEPLOYED, ready: false
INFO[2026-02-03T09:53:25Z]transformers.go:526 Pod default/dhcp-test-pod status: Phase=Pending, Containers=1/1 ready
INFO[2026-02-03T09:53:25Z]restconf_client.go:126 Checking response ...
INFO[2026-02-03T09:53:25Z]app_hosting.go:216 App cvk0000_1e08ab44a5694f3c83a287a945ccabed reached expected status: DEPLOYED
INFO[2026-02-03T09:53:25Z]app_hosting.go:170 Uninstalling app cvk0000_1e08ab44a5694f3c83a287a945ccabed
INFO[2026-02-03T09:53:25Z]app_hosting.go:141 Uninstalling app cvk0000_1e08ab44a5694f3c83a287a945ccabed
INFO[2026-02-03T09:53:26Z]app_hosting.go:148 Successfully uninstalled app cvk0000_1e08ab44a5694f3c83a287a945ccabed
INFO[2026-02-03T09:53:26Z]app_hosting.go:235 Waiting for app cvk0000_1e08ab44a5694f3c83a287a945ccabed to be removed from oper data
INFO[2026-02-03T09:53:26Z]restconf_client.go:126 Checking response ...
INFO[2026-02-03T09:53:28Z]restconf_client.go:126 Checking response ...
INFO[2026-02-03T09:53:28Z]app_hosting.go:260 App cvk0000_1e08ab44a5694f3c83a287a945ccabed no longer present in oper data
INFO[2026-02-03T09:53:28Z]app_hosting.go:178 Removing app cvk0000_1e08ab44a5694f3c83a287a945ccabed config
INFO[2026-02-03T09:53:28Z]app_hosting.go:184 Successfully deleted app cvk0000_1e08ab44a5694f3c83a287a945ccabed
INFO[2026-02-03T09:53:28Z]pod_lifecycle.go:186 Successfully deleted container test-app (app: cvk0000_1e08ab44a5694f3c83a287a945ccabed)
INFO[2026-02-03T09:53:28Z]pod_lifecycle.go:194 Pod default/dhcp-test-pod cleanup successfully completed
INFO[2026-02-03T09:53:28Z]event.go:364 Event(v1.ObjectReference{Kind:"Pod", Namespace:"default", Name:"dhcp-test-pod", UID:"1e08ab44-a569-4f3c-83a2-87a945ccabed", APIVersion:"v1", ResourceVersion:"652225", FieldPath:""}): type: 'Normal' reason: 'ProviderDeleteSuccess' Delete pod in provider successfully

In the end we do seem to clean up properly but we should adjust our workflow to handle the deactivation in a realistic way.

We also we these warnings throughout the deactivation:

WARN[2026-02-03T09:53:19Z]transformers.go:308 ARP lookup failed: no ARP entry found for MAC addresses: [52:54:dd:c5:81:99]

We should probably handle this IP discovery better. In general kubernetes does not expect POD IPs to change during their lifetime. We might need to think about how we maintain this data when using DHCP instead of constantly polling the device.

Expected Behavior

We should not expect to see warning or timeout log messages for 'normal' operations.

Actual Behavior

We are seeing warnings and timeouts during deactivation of an App.

Affected Version

Please provide the version number where this issue was encountered.

Steps to Reproduce

1. First step
2. Second step
3. etc.

Checklist

• I have read the contributing guidelines
• I have verified this does not duplicate an existing issue