Bug 984416
Summary: | GetHardwareInfoVDS fails with XmlRpcException | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Ohad Basan <obasan> |
Component: | ovirt-engine | Assignee: | Yaniv Bronhaim <ybronhei> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.3.0 | CC: | acathrow, bazulay, eedri, iheim, lpeer, obasan, Rhev-m-bugs, yeylon |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | 3.3.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | infra | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-07-23 12:27:59 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
Ohad Basan
2013-07-15 08:06:19 UTC
Ohad, Does it happen on all the hosts ? or a specific one ? This is a basic flow (getVdsCapabilities), so if it fails nothing should work. I don't know if it happens on all the host but it's certainly not a specific one. I see it on more machines. Is this a duplicate of Bug 984267 Explanation about the fix: After supervdsm crash or restart, vdsm won't be able to reach supervdsm in its next call. RuntimeError will be raised to vdsm and vdsm will try to reconnect to supervdsm, if supervdsm is up again properly, the reconnection will establish and next call between vdsm and supervdsm will work. In the bz case, setupNetwork fails due to restart of supervdsm (what should be fixed separately as part of BZ 984267), and getVdsHardwareInfo failed also (because reconnect wasn't occurred, and the connection was down). The only way to recover from that was to restart vdsmd. With the fix the next call will work after reconnect. *** This bug has been marked as a duplicate of bug 980493 *** |