Bug 1304734
Summary: | MOM- Unexpected collection error : KeyError: 'memUsage'KeyError: 'balloonInfo' when migration failed | ||||||
---|---|---|---|---|---|---|---|
Product: | [oVirt] mom | Reporter: | Shira Maximov <mshira> | ||||
Component: | General | Assignee: | Martin Sivák <msivak> | ||||
Status: | CLOSED WONTFIX | QA Contact: | Shira Maximov <mshira> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 0.4.4 | CC: | bugs, dfediuck, gklein, mshira, rgolan | ||||
Target Milestone: | --- | Keywords: | Regression | ||||
Target Release: | --- | Flags: | mshira:
planning_ack?
mshira: devel_ack? mshira: testing_ack? |
||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2016-02-17 11:36:21 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: | |||||||
Attachments: |
|
Description
Shira Maximov
2016-02-04 13:38:42 UTC
Created attachment 1121101 [details]
mom log
1) What is the VDSM version? 2) Can you test that with the latest 3.5 mom? (0.4.1-5) 3) The log appears on the destination host right? 1) vdsm-4.16.33-1.el6ev.x86_64 2) mom-0.4.1-4 is the latest, as appear in :http://bob.eng.lab.tlv.redhat.com/builds/latest_vt/el6/ 3) yes Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone. Why is it a high severity bug? What is the user consequence? I guess he's more worried about the failed migration than the traceback. (In reply to Shira Maximov from comment #3) > 3) yes If this error is on the destination server as you specify, it will have no functional impact of the failed VM, as the process is being killed. Did you notice any impact on mom's behavior? (In reply to Doron Fediuck from comment #6) > (In reply to Shira Maximov from comment #3) > > > 3) yes > > If this error is on the destination server as you specify, > it will have no functional impact of the failed VM, as the process is being > killed. > > Did you notice any impact on mom's behavior? I didn't notice any impact. That issue has no impact on the flow, no user impact. For now there is no justification in trying suppress this error. |