Created attachment 1296097 [details] screenshot Description of problem: [Text] [VM Provision] - 'Virtual Machine %{subject} has been provisioned.' The VM's name is %{subject} instead of it's real name in the event notification after provisioned is done. Version-Release number of selected component (if applicable): 5.8.1.0.20170623170756_3ed4411
Created attachment 1296098 [details] evm log
Leo, you seen this? We should be checking these and have some tests or assertions around them
Created attachment 1301655 [details] screenshot2
Leo, Curious if you made any progress on this. Please let me know. Thanks Billy
Hi Gregg, This is an odd case where the VM existed when we created the notification, but gets removed afterwards. Is there anything that can be done for the scenario where the %{subject} has been removed? Thanks, Tina
*** Bug 1511371 has been marked as a duplicate of this bug. ***
https://github.com/ManageIQ/manageiq/pull/17871
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/e587c5cf195043402d911ad57b024fedb752d50b commit e587c5cf195043402d911ad57b024fedb752d50b Author: Joe Rafaniello <jrafanie> AuthorDate: Thu Aug 16 16:42:30 2018 -0400 Commit: Joe Rafaniello <jrafanie> CommitDate: Thu Aug 16 16:42:30 2018 -0400 Backup subject's name in case subject is removed Fixes a bug where notifications look like the following if the subject vm has been removed: 'Virtual Machine %{subject} has been provisioned.' https://bugzilla.redhat.com/show_bug.cgi?id=1469372 app/models/notification.rb | 11 + spec/models/notification_spec.rb | 38 + 2 files changed, 49 insertions(+)
Fixed! Verifying on version: 5.10.0.24.20181113213923_03b81fd No error occurred in notification message after deleting 'provision request' and 'VM' from database(vmdb).
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:0212