Bug 879923
| Summary: | engine: each time ovirt-engine service is restarted we get "Invalid status on Data Center" in event log | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Dafna Ron <dron> | ||||
| Component: | ovirt-engine | Assignee: | Barak <bazulay> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Pavel Stehlik <pstehlik> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 3.1.0 | CC: | acathrow, hateya, iheim, jkt, lpeer, Rhev-m-bugs, yeylon, yzaslavs | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | infra | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-12-29 10:54:13 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: | |||||||
| Attachments: |
|
||||||
IMHO, setting an event for the case the engine is shutting down is not that trivial and requires some code change. I am postponing this to future. Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug. |
Created attachment 651526 [details] screen shot Description of problem: each time engine service is restarted we get a warning in event log that "Invalid status on Data Center X. Invalid status on Data Center. since we see it only after the service has started and we logged in again, I don't think this is the correct warning. Version-Release number of selected component (if applicable): si24.4 How reproducible: 100% Steps to Reproduce: 1. restart ovirt-engine service 2. 3. Actual results: warning in event log: Invalid status on Data Center X. Setting status to Non-Responsive. Expected results: 1. I think we should move this warning from event log since the user cannot login when the engine is down and will only see it once everything is back to normal. 2. if possible, I would add a warning that the service is going down and a second one when its going up (that way we can also wee how long engine was down). Additional info: screen shot