Bug 1553126
| Summary: | Automatic network sync floods webadmin's Notification Drawer with events | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Dominik Holler <dholler> | 
| Component: | BLL.Network | Assignee: | Dominik Holler <dholler> | 
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Mor <mkalfon> | 
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.2.1.7 | CC: | bugs, lveyde, mkalfon | 
| Target Milestone: | ovirt-4.2.2 | Flags: | rule-engine:
                ovirt-4.2+ | 
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ovirt-engine-4.2.2.4 | Doc Type: | Bug Fix | 
| Doc Text: | Cause: Every execution of the automatic network synchronization reports the result to audit log.
Consequence: Even if no new network is imported or an external network provider is not configured correctly, new events are added to the webadmin's Notification Drawer and the audit log every time the sync is triggered, which is every 5 minutes by default.
Fix: Failed execution of the automatic network synchronization are reported only once a day, if the synchronization detects nothing to sync, nothing is reported.
Result: If no new network is imported or removed no new events are added to the webadmin's Notification Drawer and the audit log.
If the synchronization fails, only once a day an event is reported. | Story Points: | --- | 
| Clone Of: | Environment: | ||
| Last Closed: | 2018-03-29 10:54:27 UTC | Type: | Bug | 
| Regression: | --- | Mount Type: | --- | 
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Network | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| 
        
          Description
        
        
          Dominik Holler
        
        
        
        
        
          2018-03-08 11:13:00 UTC
        
       Verified on: RHV 4.2.2.4-0.1.el7 This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |