Bug 1406622
| Summary: | [HE - Logging] Improve logging of uptodate score | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Germano Veit Michel <gveitmic> | |
| Component: | ovirt-hosted-engine-ha | Assignee: | Denis Chaplygin <dchaplyg> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Nikolai Sednev <nsednev> | |
| Severity: | high | Docs Contact: | ||
| Priority: | medium | |||
| Version: | 3.6.9 | CC: | bmcclain, dfediuck, lsurette, msivak, ykaul, ylavi | |
| Target Milestone: | ovirt-4.1.2 | Keywords: | Improvement, Triaged, ZStream | |
| Target Release: | --- | Flags: | gklein:
testing_plan_complete-
|
|
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1432880 (view as bug list) | Environment: | ||
| Last Closed: | 2017-06-07 13:32:47 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | SLA | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1432880 | |||
|
Description
Germano Veit Michel
2016-12-21 04:51:02 UTC
It's actually: ovirt-hosted-engine-ha-1.3.5.8-1.el7ev.noarch This is more of a debugging level, than standard logging output. So when implementing please ensure it gets the relevant log level. 3.5->3.6 upgrade flow should provide the reproduction, see https://bugzilla.redhat.com/show_bug.cgi?id=1337960 and if it will be hit, then this bug fix should report ['not-uptodate-config-penalty'] with 2400 score (penalty of 1000). But if you won't back-port this fix to 3.6, then only after 3.6->4.0 upgrade, the fix would be verified. Forth to results received in bug#1432880, I've got the same results aslo for latest 4.1.2. Moving to verified. Bronce, any idea why it's not closed-currentrelease? (In reply to Yaniv Kaul from comment #10) > Bronce, any idea why it's not closed-currentrelease? It obviously missed an errata and I didn't mark it closed. I'll do that now. |