Workaround:
- The workaround is to find the notification schedules from old deleted (rogue) environment of the VMware Aria Suite Lifecycle and delete them
- Steps below :
- Ensure proper snapshots and the backup of the VMware Aria Suite Lifecycle appliance and database.
- Login to the VMware Aria Suite Lifecycle as root.
- Navigate to its database:
su - postgres
cd /opt/vmware/vpostgres/11/bin/
./psql -d vrlcm
- We could see from the database the old entries for environments which does not exist on UI.
select environmentname from vm_lcops_environment;
- Lets say my deleted/rogue environment is 'vRealize' and notifications are coming from this environment.
- Find out the notifications from this old deleted environment by running query:
select vmid from vm_engine_scheduledrequest ;
- Delete those old notifications schedules (lets say the problematic notification schedule is 'vra,8.11.0,productPatchingNotification,vRealize'):
delete from vm_engine_scheduledrequest where vmid='vra,8.11.0,productPatchingNotification,vRealize' ;
- Monitor the notifications on VMware Aria Suite Lifecycle UI for next 24 hours and it should not be triggered any longer.