Bug 1400500
| Summary: | If AvailableUpdatesFinder finds already running process it should not be ERROR level | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Jiri Belka <jbelka> |
| Component: | BLL.Infra | Assignee: | Moti Asayag <masayag> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Lucie Leistnerova <lleistne> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.0.6.2 | CC: | bugs, lleistne, masayag, mperina, oourfali |
| Target Milestone: | ovirt-4.1.1 | Flags: | rule-engine:
ovirt-4.1+
rule-engine: planning_ack+ masayag: devel_ack+ pstehlik: testing_ack+ |
| Target Release: | 4.1.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-04-21 09:38:37 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
Jiri Belka
2016-12-01 11:51:54 UTC
We do use alert. I find this use-case not that interesting, but I'm leaving the decision here to Moti. We can reduce the severity of that message from ERROR to WARN. ovirt-engine-backend-4.1.0.1-0.1.el7.noarch [root@jbelka-vm2 yum.repos.d]# grep -i 'message:.*another refresh process is already running' /var/log/ovirt-engine/engine.log 2017-01-24 11:57:56,214+01 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (pool-5-thread-3) [29b090ae] EVENT_ID: HOST_AVAILABLE_UPDATES_FAILED(839), Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Failed to check for available updates on host dell-r210ii-04 with message 'Another refresh process is already running'. 2017-01-24 11:57:57,682+01 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (pool-5-thread-4) [1fa56e70] EVENT_ID: HOST_AVAILABLE_UPDATES_FAILED(839), Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Failed to check for available updates on host dell-r210ii-04 with message 'Another refresh process is already running'. 2017-01-24 11:57:59,082+01 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (pool-5-thread-5) [2858eb5b] EVENT_ID: HOST_AVAILABLE_UPDATES_FAILED(839), Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Failed to check for available updates on host dell-r210ii-04 with message 'Another refresh process is already running'. 2017-01-24 11:58:00,508+01 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (pool-5-thread-6) [22695697] EVENT_ID: HOST_AVAILABLE_UPDATES_FAILED(839), Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Failed to check for available updates on host dell-r210ii-04 with message 'Another refresh process is already running'. [root@jbelka-vm2 yum.repos.d]# grep -i 'WARN.*another refresh process is already running' /var/log/ovirt-engine/engine.log 2017-01-24 11:57:56,209+01 WARN [org.ovirt.engine.core.bll.hostdeploy.HostUpdatesChecker] (pool-5-thread-3) [29b090ae] Failed to refresh host 'dell-r210ii-04' packages availability, another refresh process is already running. 2017-01-24 11:57:57,674+01 WARN [org.ovirt.engine.core.bll.hostdeploy.HostUpdatesChecker] (pool-5-thread-4) [1fa56e70] Failed to refresh host 'dell-r210ii-04' packages availability, another refresh process is already running. 2017-01-24 11:57:59,072+01 WARN [org.ovirt.engine.core.bll.hostdeploy.HostUpdatesChecker] (pool-5-thread-5) [2858eb5b] Failed to refresh host 'dell-r210ii-04' packages availability, another refresh process is already running. 2017-01-24 11:58:00,500+01 WARN [org.ovirt.engine.core.bll.hostdeploy.HostUpdatesChecker] (pool-5-thread-6) [22695697] Failed to refresh host 'dell-r210ii-04' packages availability, another refresh process is already running. Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release. engine=# select severity,log_type_name,message from audit_log where message like '%Another refresh process is already running%';
severity | log_type_name | message
----------+-------------------------------+-------------------------------------------------------------------------------------------------------------------------
2 | HOST_AVAILABLE_UPDATES_FAILED | Failed to check for available updates on host dell-r210ii-04 with message 'Another refresh process is already running'.
2 | HOST_AVAILABLE_UPDATES_FAILED | Failed to check for available updates on host dell-r210ii-04 with message 'Another refresh process is already running'.
2 | HOST_AVAILABLE_UPDATES_FAILED | Failed to check for available updates on host dell-r210ii-04 with message 'Another refresh process is already running'.
2 | HOST_AVAILABLE_UPDATES_FAILED | Failed to check for available updates on host dell-r210ii-04 with message 'Another refresh process is already running'.
(4 rows)
Ok, I understand the point: There is a need to separate the event type for the both cases: failure to update as a result of another running upgrade process and any other failure. For that purpose I'll introduce another audit log type for the specific case of another running process with a WARNING severity. The log entries which aren't related to the event-log in the engine.log were already reduced to warn severity. log entries for already running upgradecheck changed are WARN verified in ovirt-engine-4.1.1.2-0.1.el7.noarch |