Manual Infra classification (by user) is lost after a day

Products

• VMware vDefend Firewall with Advanced Threat Prevention
• VMware vDefend Firewall

Issue/Introduction

You are running NSX Application Platform (NAPP), and you have updated a workload that currently shows as "Classification Pending" to "Infra". The next day, you revisit the Plan & Troubleshoot → Preferences page, and the workload you previously classified is now once again listed as "Classification pending"

Environment

NAPP 4.2 and prior

Cause

VM's which were classified  manually by the user were persisted with the last_classified_time_interval as 0 in workload DB. Due to this, workload purge job assumed these vms as stale (more than 90 days)  and  cleaned up the entries from classification table, which made all manually classified vms  into "classification pending state".

Resolution

Set the optional field "description" on the dialogue for classification review. This will ensure that the manually edited classification is not purged.

Additionally, ensure that that the KB for removing stale workload entries is applied to the environment:

https://knowledge.broadcom.com/external/article?articleNumber=378826

 

Without this, it is possible for workloads classified by the user (with the description field set as detailed above), will reside in the database longer than intended.