Bug 1994144
Summary: | [RHV 4.4.6] Mail recipient is not updated while configuring Event Notifications | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Chetan Nagarkar <cnagarka> |
Component: | ovirt-engine | Assignee: | Eli Mesika <emesika> |
Status: | CLOSED ERRATA | QA Contact: | Guilherme Santos <gdeolive> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.4.6 | CC: | apinnick, emesika, lsvaty, mavital, mperina, shaselde, usurse |
Target Milestone: | ovirt-4.5.1 | Keywords: | ZStream |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | ovirt-engine-4.5.0 | Doc Type: | Bug Fix |
Doc Text: |
The email address for notifications is updated correctly on the "Manage Events" screen.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2022-07-14 12:54:30 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Chetan Nagarkar
2021-08-16 21:20:44 UTC
The best way is to have a valid email address in LDAP for all users. Then this address is used for mail notification and there is no need to override it in webadmin Verified on ovirt-engine-4.5.0.6-0.7.el8ev.noarch Followed steps 1-7 and Mail Recipient displayed in the window is the one entered beforehand 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 (Moderate: RHV Manager (ovirt-engine) [ovirt-4.5.1] security, bug fix and update), 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-2022:5555 Due to QE capacity, we are not going to cover this issue in our automation The customer upgraded to ovirt-engine-4.5.1.3-0.28.el8ev.noarch and we still see this issue. Is it possible there was a regression? |