Bug 996970 - Changing email address for event notification results in error "User is already subscribed to this event with the same Notification method"
Summary: Changing email address for event notification results in error "User is alrea...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-webadmin-portal
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: 3.2.3
Assignee: Ravi Nori
QA Contact: Ilanit Stein
URL:
Whiteboard: infra
Depends On: 985635
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-14 11:35 UTC by Idith Tal-Kohen
Modified: 2018-12-03 19:41 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Changing an email address for receiving event notifications failed with the message that the user was already subscribed. This occurred because the RemoveEventSubscription action did not complete before AddEventSubscription was called. This update ensures that the calls are invoked in sequence, so changing email addresses for event notification succeeds.
Clone Of: 985635
Environment:
Last Closed: 2013-09-10 19:06:25 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 475413 0 None None None Never
Red Hat Product Errata RHSA-2013:1210 0 normal SHIPPED_LIVE Moderate: rhevm security and bug fix update 2013-09-10 23:03:43 UTC
oVirt gerrit 17984 0 None None None Never

Comment 2 Ilanit Stein 2013-08-25 13:11:41 UTC 
Verified on sf20
Comment 4 errata-xmlrpc 2013-09-10 19:06:25 UTC 
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.

http://rhn.redhat.com/errata/RHSA-2013-1210.html
Note You need to log in before you can comment on or make changes to this bug.