AE-2381 : vAPV Device in AMP Volume License are Not Getting Reconnected After the vAPV is Rebooted.

Review Request #1350 — Created Jan. 30, 2026 and submitted — Latest diff uploaded

pmurugaiyan
AMP
amp_3_7_2
AE-2381
apoorva.sn, pradeep, shuinvy

Issue: License Managed Devices showed incorrect "unconnected" status after reboot and lost their activationserver configuration.

RCA:

Monitoring Gap: The taskscheduler only queried the device table, failing to monitor connection status for License Managed Devices (stored in device2).

Configuration Loss: Devices reset their activationserver settings upon reboot, and the AMP server had no mechanism to restore this automatically.

Fix: Updated the scheduler to monitor active device2 entries and implemented an auto-recovery mechanism that triggers device re-registration (restoring activationserver) immediately upon detecting connection recovery. Also hardened task_scheduler.py to handle device2 types, bypass unnecessary locks, and update the correct database tables/caches.

The changes has been tested locally.


    Loading...