[BUG-NOK] Open Edge Orchestrator - "Status: Unknown” shown only for a specific device

[nagarjunaha056]

Bug Description

In the Open Edge Orchestrator → Deployments tab, the Status column consistently shows “Unknown” only for one specific device.
For other devices, deployment statuses are correctly displayed as “Running” or “No target_clusters(for deleted clusters)”.

System Setup

Open Edge Orchestrator 3.1.3

Reproducible Steps

Steps to Reproduce:

1. Go to Deployments page.
2. Observe the list of deployments (refer to attached screenshot).
3. Check the Status column for all devices.
4. Notice that for a particular device, all deployments show “Unknown”, even after multiple successful onboardings.

Expected Behavior
Deployment Status should correctly display as “Running”, “Failed”, or “No target_clusters” depending on the current state of the application.

Actual Behavior
For one specific device:

1. Status appears as “Unknown” for most or all deployments.
2. Other devices show proper status (e.g., “Running”).
3. The issue persists even after multiple onboardings of the affected device.

Frequency:
Occurs consistently for the same device.

Root Cause Analysis

No response

[nagarjunaha056]

Cluster is also in running state

The edge node is up and running

[guptagunjan]

The device showing "Unknown" status has its Fleet agent that hasn't sent a heartbeat > 30 minutes. Common reasons:

• Network connectivity issues
• Fleet agent crashed
• Time sync issues
• The node itself is having problems

@nagarjunaha056

1. can you check Fleet agent status on the device and share us the logs(kubectl logs -n cattle-fleet-system )
2. Check cluster connectivity
3. Check last heartbeat time(kubectl get cluster -n -o jsonpath='{.status.agent.lastSeen}')
4. App deployment manager pod logs