The issue occurs as the scheduled upgrade notification requests that are created in the database for the products are not updated anytime an upgrade is performed. This results in stale notifications being sent in relation to the versions that were applicable only at time of the initial environment creation or import.
1. Take a Snapshot of the vRealize Suite Lifecycle Manager appliance
2. Connect to the postgres database, Ssh to the appliance, login with root user and run the commands:
su - postgres
cd /opt/vmware/vpostgres/11/bin
./psql vrlcm
3. To identify the row with the incorrect version numbers run the select query:
select * from vm_engine_scheduledrequest;
4. Delete the entry for scheduled_request (This entry will have the older product version )
delete FROM public.vm_engine_scheduledrequest where vmid like '%productname%productUpgradeNotification%{environment-name}%';
5. Delete the upgraded product from vRealize Suite Lifecycle Manager. Note: Be sure to leave the Delete associated VMs from vCenter checkbox blank, otherwise the machines will be deleted in vCenter.
6. Import again the product into vRealize Suite Lifecycle Manager. This will create a new scheduled request for product upgrade notification on the correct version.